From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] wireshark: remove RPATH tag
Date: Wed, 5 Nov 2014 08:31:24 +0100 [thread overview]
Message-ID: <20141105083124.57a5d559@free-electrons.com> (raw)
In-Reply-To: <20141105072214.GL2358@sapphire.tkos.co.il>
Dear Baruch Siach,
On Wed, 5 Nov 2014 09:22:14 +0200, Baruch Siach wrote:
> > Isn't this problem potentially identical in many packages that use
> > libtool? What leads the wireshark libtool to have this specifically?
>
> Probably. The Buildorot speex package does an almost identical edit to its own
> libtool. Do you think we should enable this for all libtool users? We'll only
> know if anything breaks at run time.
Well, not having a rpath should not break things at runtime, unless a
custom rpath is really necessary. But I'm pretty sure in those cases,
the custom rpath will be wrong as it will point to some location on the
build machine.
What would be good is to understand why in certain situations libtool
decides to set a rpath and not in other cases.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-11-05 7:31 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 [this message]
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
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=20141105083124.57a5d559@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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