From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: RPATH in many modules
Date: Sat, 02 Oct 2010 19:02:17 -0700 [thread overview]
Message-ID: <4CA7E429.7060407@mentor.com> (raw)
In-Reply-To: <AANLkTi=e0PuBjz1o-FhmaE7Mh_+JOLOau7ZhC0G9WOBn@mail.gmail.com>
Khem Raj wrote:
> On Sat, Oct 2, 2010 at 4:39 AM, Holger Freyther <holger+oe@freyther.de> wrote:
>> Hi all,
>>
>> today I wanted to make the generated toolchain free of RPATH and I was a bit
>> surprised to see that even the target libraries contain the rpath and that it
>> is not caught by insane.bbclass.
>>
>> I have added a more strict check to insane.bbclass to uncover the issue and I
>> am fighting neon and its manual libtool usage right now... it might be just
>> easier to use chrpath to fix the resulting libraries.
>>
>> any opinion?
>
> I think we should try to get the rpaths right without chrpath. so your
> insane patch
> seems ok. May be to avoid lot of packages failing this could be turned
> on as a warning
> and once we fix the packages failing this then we could turn it into error.
Initial link time $ORIGIN being correct is a lot more complex than being
wrong and fixing it up. I got it being correct for the non-autoconf
case and then made autotools.bbclass also get it right initially and
then patched gcc/gdb/binutils (which are the difficult ones that run
configure again) but it's really much more work. I'll try and RFC the
patches on Monday, if I've still got the branch around.
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2010-10-03 2:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-02 11:39 RPATH in many modules Holger Freyther
2010-10-02 20:34 ` Khem Raj
2010-10-03 2:02 ` Tom Rini [this message]
2010-10-03 7:24 ` Koen Kooi
2010-10-03 7:32 ` Holger Freyther
2010-10-03 7:37 ` Koen Kooi
2010-10-03 20:46 ` Khem Raj
2010-10-04 21:08 ` Denys Dmytriyenko
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=4CA7E429.7060407@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-devel@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.