From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] binutils now adds sysroot for ld -rpath search
Date: Wed, 15 Mar 2017 08:45:00 +0100 [thread overview]
Message-ID: <1489563900.12464.2.camel@embedded.rocks> (raw)
In-Reply-To: <20170314222024.7fe9af37@free-electrons.com>
Hi Thomas,
On Tue, 2017-03-14 at 22:20 +0100, Thomas Petazzoni wrote:
> Hello,
>
> On Tue, 14 Mar 2017 10:33:58 +0100, J?rg Krause wrote:
>
> > After a discussion with Brad King on the CMake issue tracker [1]
> > about
> > how the linker should handle -rpath we agreed that ld should add
> > the
> > sysroot when searching for files (but not when setting the RPATH
> > header
> > value).
> >
> > I picked up a five years old patch from the binutils mailing list
> > [2]
> > which already proposed the change, but was not submitted then.
> >
> > I resend the patch [3] and this time Alan Modra accepted the
> > change. He
> > submitted two patches [4,5] which will add the sysroot to
> > -rpath?for
> > absolute paths.
>
> Aaah indeed. I also recently looked at some package that was failing
> to
> build because -rpath /usr/lib was passed. And then I realized that
> things were clunky: what if you really a RPATH to be encoded in the
> generated binary, but don't want this path to be looked at on the
> build
> machine during the cross-compilation.
>
> Your patch solves exactly that. I guess we'll have to integrate it in
> Buildroot as well, but we will still have issues with external
> toolchains, sadly :-/
For now! But someday in the future all toolchains will use binutils at
least 2.29 (which will have the patch).
> Thanks a lot for this work!
>
You're welcome! I just wanted to understand what the issue with rpath
is. I'm glad it will cause less trouble (when all toolchains are
updated).
Best regards,
J?rg
prev parent reply other threads:[~2017-03-15 7:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 9:33 [Buildroot] binutils now adds sysroot for ld -rpath search Jörg Krause
2017-03-14 21:20 ` Thomas Petazzoni
2017-03-15 7:45 ` Jörg Krause [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=1489563900.12464.2.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--cc=buildroot@busybox.net \
/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