redundant RPATH warning?

redundant RPATH warning?

[Kumar Gala]

What causes warnings like the following:

WARNING: QA Issue: gthumb: /work/ppce5500-poky-linux/gthumb-2.12.3-r1/packages-split/gthumb/usr/lib64/gthumb/extensions/libexport_tools.so contains probably-redundant RPATH /usr/lib64

Is this something we should by trying to clean up?

- k

Re: redundant RPATH warning?

[Phil Blundell]

On Wed, 2011-08-03 at 10:00 -0500, Kumar Gala wrote:
> What causes warnings like the following:
> 
> WARNING: QA Issue: gthumb: /work/ppce5500-poky-linux/gthumb-2.12.3-r1/packages-split/gthumb/usr/lib64/gthumb/extensions/libexport_tools.so contains probably-redundant RPATH /usr/lib64

Pretty much what it says.  That DSO contains an RPATH record pointing to
a directory which (in insane.bbclass's view) the dynamic linker would
have searched anyway without being told to.  In most cases this means
that the RPATH isn't serving any useful purpose and is just wasting time
and space.

Obviously insane.bbclass is not infallible though.  In particular, there
is no portable way to find out what paths ld.so will actually search on
its own initiative, so insane.bbclass assumes that the list consists of
${base_libdir} and ${libdir}.  If that assumption isn't valid in your
particular configuration then you will get spurious warnings.

> Is this something we should by trying to clean up?

Ideally, yes.  I think libtool is the main offender in this respect and,
if it could be fixed somehow, the majority of those warnings would
probably go away.

p.

Re: redundant RPATH warning?

[Mark Hatle]

On 8/3/11 10:00 AM, Kumar Gala wrote:
> What causes warnings like the following:
> 
> WARNING: QA Issue: gthumb: /work/ppce5500-poky-linux/gthumb-2.12.3-r1/packages-split/gthumb/usr/lib64/gthumb/extensions/libexport_tools.so contains probably-redundant RPATH /usr/lib64

Something passing in rpath /usr/lib64 during linking.. likely libtool....

> Is this something we should by trying to clean up?

It doesn't have to be cleaned up, but it's a really good idea to find and fix
the problems.  I believe that the standard libtool in oe-core avoids passing
rpaths of standard system prefixes.. so it's likely the gthumb Makefiles
themselves that are doing this.  (Unless of course libtool has a bug....)

--Mark

> - k
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core