From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] wireshark: remove RPATH tag
Date: Sun, 5 Apr 2015 11:05:00 +0200 [thread overview]
Message-ID: <20150405090500.GA4134@free.fr> (raw)
In-Reply-To: <20150404195923.154d3366@free-electrons.com>
Thomas, All,
On 2015-04-04 19:59 +0200, Thomas Petazzoni spake thusly:
> On Tue, 4 Nov 2014 20:35:41 +0200, Baruch Siach wrote:
> > Edit libtool to remove RPATH from generated binaries. This is similar to
> > upstream commit making the same change when buiding RPMs.
> > https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commitdiff;h=a4a624e4c5
> >
> > Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> > ---
> > package/wireshark/wireshark.mk | 6 ++++++
> > 1 file changed, 6 insertions(+)
>
> I'm still not sure what to do with this. Yann, Gustavo, Samuel, some
> suggestions ?
>
> Should we introduce a final check in target-finalize to warn about
> binaries having invalid rpaths, and start fixing them one by one ? Or a
> more brutal approach where we remove all rpaths in target-finalize ?
I have a series doing exactly that; I'll be sending it shortly.
> I'm a bit uncomfortable with having a fix for just one package without
> having a globally defined policy on how to handle this rpath mess.
> Opinions welcome.
I feel the same.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2015-04-05 9:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 18:35 [Buildroot] [PATCH] wireshark: remove RPATH tag Baruch Siach
2014-11-05 7:15 ` Thomas Petazzoni
2014-11-05 7:22 ` Baruch Siach
2014-11-05 7:31 ` Thomas Petazzoni
2014-11-17 12:33 ` Baruch Siach
2014-11-17 12:45 ` Gustavo Zacarias
2014-11-17 13:32 ` Samuel Martin
2014-11-17 13:38 ` Baruch Siach
2015-04-04 17:59 ` Thomas Petazzoni
2015-04-05 9:05 ` Yann E. MORIN [this message]
2015-04-05 9:29 ` Thomas Petazzoni
2015-04-05 10:06 ` Yann E. MORIN
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150405090500.GA4134@free.fr \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox