From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Bug in RPATH fixing logic
Date: Sun, 12 Nov 2017 18:24:03 +0100 [thread overview]
Message-ID: <20171112182403.5d5c8fe4@windsurf.home> (raw)
In-Reply-To: <87y3nbs9jz.fsf@dell.be.48ers.dk>
Hello,
On Sun, 12 Nov 2017 18:15:12 +0100, Peter Korsgaard wrote:
> > So this happens because the ARC binutils version is fetched from Git,
> > so we need to have host-flex installed, and binutils detects the flex
> > library and decides to use it.
>
> And there is no configure flag to disable that?
Not that I can see.
> >> - The absolute rpath in $(HOST_DIR)/<tuple>/bin/ar is wrong in the
> >> first place, but I'm not sure how to fix this.
>
> > I'm wrong on this: $(HOST_DIR)/<tuple>/bin/ar RPATH is totally fine:
>
> > $ readelf -d arc-buildroot-linux-uclibc/bin/ar | grep rpath
> > 0x000000000000000f (RPATH) Library rpath: [/opt/br-arcle-hs38-full-2017.11-rc1/lib]
>
> > The problem is that this gets turned into $ORIGIN/../lib by patchelf.
>
> > I don't see any other solution than de-duplicating such binaries.
>
> > Do you see another option ?
>
> Not if we *need* both binaries (do we?)
I think we do need both binaries. <tuple>-<tool> is the "publicly"
visible copy, while <tuple>/bin/<tool> is the one called internally by
gcc (for example when it calls as or ld). Yann can explain more about
this perhaps.
> Is there a way to get binutils to use soft links instead of hard links?
How would this solve the problem?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-11-12 17:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-12 16:40 [Buildroot] Bug in RPATH fixing logic Thomas Petazzoni
2017-11-12 16:49 ` Thomas Petazzoni
2017-11-12 17:15 ` Peter Korsgaard
2017-11-12 17:24 ` Thomas Petazzoni [this message]
2017-11-12 17:42 ` Yann E. MORIN
2017-11-13 7:17 ` Wolfgang Grandegger
2017-11-13 13:50 ` Peter Korsgaard
2017-11-13 15:19 ` Wolfgang Grandegger
2017-11-13 17:36 ` Yann E. MORIN
2017-11-13 18:04 ` Wolfgang Grandegger
2017-11-13 20:23 ` Peter Korsgaard
2017-11-13 20:33 ` Yann E. MORIN
2017-11-14 8:00 ` Wolfgang Grandegger
2017-11-14 9:05 ` Wolfgang Grandegger
2017-11-14 10:39 ` Peter Korsgaard
2017-11-12 18:03 ` Peter Korsgaard
2017-11-12 19:04 ` Wolfgang Grandegger
2017-11-12 19:35 ` Wolfgang Grandegger
2017-11-12 20:37 ` Thomas Petazzoni
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=20171112182403.5d5c8fe4@windsurf.home \
--to=thomas.petazzoni@free-electrons.com \
--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