From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: redundant RPATH warning?
Date: Wed, 3 Aug 2011 10:11:14 -0500 [thread overview]
Message-ID: <4E396512.9090605@windriver.com> (raw)
In-Reply-To: <1D9491FE-2F9E-4AE5-B176-117DDD21BAE0@kernel.crashing.org>
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
prev parent reply other threads:[~2011-08-03 15:15 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
2011-08-03 15:11 ` Mark Hatle [this message]
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=4E396512.9090605@windriver.com \
--to=mark.hatle@windriver.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.