[Buildroot] [PATCH] wireshark: remove RPATH tag
Baruch Siach
baruch at tkos.co.il
Mon Nov 17 12:33:15 UTC 2014
Hi Thomas,
On Wed, Nov 05, 2014 at 08:31:24AM +0100, Thomas Petazzoni wrote:
> 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.
It seems that libtool decides to set rpath based on .la files we have in
staging. Some of them (e.g. glib provided libs, and libnl) set either
'dependency_libs' (glib) or 'libdir' (libnl) to paths under output/build or
staging. wireshark also links its own libraries (e.g. wiretap, epan) using
local source tree .la files. I'm not sure how to solve this in the general
case. It probably requires fixing up all these .la files.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
More information about the buildroot
mailing list