Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFCv1 2/4] core: change host RPATH handling
Date: Sun, 5 Nov 2017 15:44:20 +0100	[thread overview]
Message-ID: <20171105154420.52d67acd@windsurf.home> (raw)
In-Reply-To: <20171105085756.GG2996@scaer>

Hello,

On Sun, 5 Nov 2017 09:57:56 +0100, Yann E. MORIN wrote:

> In the past, we explicitly got rid of LD_LIBRARY_PATH because it does
> not work. See 34d081674a (core/pkg-infrastructures: remove LD_LIBRARY_PATH
> from the environment).
> 
> Briefly, it does not work when we build a library that is also present
> on the distro, which is used by a tool from the distro, and we build it
> in an incompatibl way.
> 
> So, we'll have to come up with another solution, like your suggested
> alternative.
> 
> >  - At the end of the build, in order to make sure that binaries are
> >    usable without LD_LIBRARY_PATH, we fixup the host binaries to use
> >    $ORIGIN/../lib. This is more-or-less what was done previously in
> >    the "make sdk" target, except that instead of turning absolute
> >    paths into relative paths in the RPATH, we are simply setting the
> >    RPATH to $ORIGIN/../lib.
> > 
> >    In order to implement this, the fix-rpath script logic is adjusted
> >    for the "host" case.
> > 
> > An alternative strategy would have been to keep the
> > -Wl,-rpath,$(HOST_DIR) flag, and therefore the absolute RPATH in the
> > host binaries, and fix such RPATH at the end of the build of every
> > package. However, that would require calling fix-rpath after the
> > installation of every package, which is a bit expensive.  
> 
> I wonder how expensive that would be. It would be nice to time this.
> 
> Also note that, even if the overhead is noticeable, this would be
> compensated by the mere fact that we are now doing a parallel build, so
> we would end up winning.

Thanks for the feedback. We already discussed this on IRC, and I agree.
I'll have a look at implementing the solution of doing the patchelf
adding $ORIGIN/../lib as an RPATH directly after the installation of
each package.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-11-05 14:44 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-03 16:06 [Buildroot] [RFCv1 0/4] Per-package SDK and target directories Thomas Petazzoni
2017-11-03 16:06 ` [Buildroot] [RFCv1 1/4] pkgconf: use relative path to STAGING_DIR instead of absolute path Thomas Petazzoni
2017-11-07 21:05   ` Arnout Vandecappelle
2017-11-03 16:06 ` [Buildroot] [RFCv1 2/4] core: change host RPATH handling Thomas Petazzoni
2017-11-05  8:57   ` Yann E. MORIN
2017-11-05 14:44     ` Thomas Petazzoni [this message]
2017-11-05 14:48       ` Arnout Vandecappelle
2017-11-07 22:41     ` Thomas Petazzoni
2017-11-07 23:50       ` Arnout Vandecappelle
2017-11-08  8:55         ` Thomas Petazzoni
2017-11-08 10:55           ` Arnout Vandecappelle
2017-11-08 12:30             ` Thomas Petazzoni
2017-11-08 12:38               ` Arnout Vandecappelle
2017-11-07 21:15   ` Arnout Vandecappelle
2017-11-07 21:22     ` Thomas Petazzoni
2017-11-07 23:45       ` Arnout Vandecappelle
2017-11-03 16:06 ` [Buildroot] [RFCv1 3/4] toolchain: post-pone evaluation of TOOLCHAIN_EXTERNAL_BIN Thomas Petazzoni
2017-11-07 21:23   ` Arnout Vandecappelle
2017-11-07 21:33     ` Thomas Petazzoni
2017-11-07 23:49       ` Arnout Vandecappelle
2017-11-03 16:06 ` [Buildroot] [RFCv1 4/4] core: implement per-package SDK and target Thomas Petazzoni
2017-11-07 22:50   ` Arnout Vandecappelle
2017-11-07 23:11     ` Thomas Petazzoni
2017-11-07 23:57       ` Arnout Vandecappelle
2017-11-24 14:49         ` Thomas Petazzoni
2017-11-24 14:43     ` Thomas Petazzoni
2017-11-25 17:30       ` Arnout Vandecappelle
2017-11-25 20:01         ` Thomas Petazzoni
2017-11-27 14:23           ` Yann E. MORIN
2017-11-07 23:21 ` [Buildroot] [RFCv1 0/4] Per-package SDK and target directories Arnout Vandecappelle

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=20171105154420.52d67acd@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