From: Saul Wold <sgw@linux.intel.com>
To: Andy Ross <andy.ross@windriver.com>
Cc: openembedded-core@openembedded.org
Subject: Re: [PATCH 0/2] RPATH fixes: libtool & binutils
Date: Fri, 24 Aug 2012 11:40:42 -0700 [thread overview]
Message-ID: <5037CAAA.70603@linux.intel.com> (raw)
In-Reply-To: <1345743151-2065-1-git-send-email-andy.ross@windriver.com>
On 08/23/2012 10:32 AM, Andy Ross wrote:
> Current RPATH work:
>
> Patch 1 just updates the libtool work to use the built-in
> normalization function instead of sed, as requested.
>
> Patch 2 is to binutils ld, to fix the underlying host pollution issue:
> the -rpath argument was not sysroot aware, so setting
> "/usr/lib/../lib" as an RPATH would add the host /usr/lib to the link
> time search path instead of the sysroot directory.
>
> Note that the previous warning fix to insane.bbclass is still
> producing unmasked warnings in a few cases (the rpm utilities are one
> that I know), mostly in programs instead of libraries. These will
> need to be audited independently. It's possible that they are liking
> with -rpath directly and not using libtool, or that a needed
> normalization in libtool is still missing. But with the current
> patches these warnings are benign now, they can't break the build.
>
> Andy
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
Merged this patch set into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2012-08-24 18:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 17:32 [PATCH 0/2] RPATH fixes: libtool & binutils Andy Ross
2012-08-23 17:32 ` [PATCH 1/2] libtool: update rpath normalization to use builtin Andy Ross
2012-08-23 17:32 ` [PATCH 2/2] ld: -rpath must search under sysroot Andy Ross
2012-08-24 18:40 ` Saul Wold [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=5037CAAA.70603@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=andy.ross@windriver.com \
--cc=openembedded-core@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