Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: redundant RPATH warning?
Date: Wed, 03 Aug 2011 16:08:40 +0100	[thread overview]
Message-ID: <1312384121.4325.90.camel@phil-desktop> (raw)
In-Reply-To: <1D9491FE-2F9E-4AE5-B176-117DDD21BAE0@kernel.crashing.org>

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.





  reply	other threads:[~2011-08-03 15:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-03 15:00 redundant RPATH warning? Kumar Gala
2011-08-03 15:08 ` Phil Blundell [this message]
2011-08-03 15:11 ` Mark Hatle

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=1312384121.4325.90.camel@phil-desktop \
    --to=philb@gnu.org \
    --cc=openembedded-core@lists.openembedded.org \
    /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