From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] Relocatable host tools
Date: Fri, 11 Dec 2015 16:28:50 +0100 [thread overview]
Message-ID: <20151211162850.327b9e71@free-electrons.com> (raw)
In-Reply-To: <CAAXf6LX2uJ7p+SzdZq2LKL0JsHXB0PzO_1Lx5tTjcBfDq-7wZg@mail.gmail.com>
Thomas,
On Fri, 11 Dec 2015 15:11:27 +0100, Thomas De Schampheleire wrote:
> I believe this is one step closer to having a relocatable host SDK for
> Buildroot. While I'm not claiming (nor have I tested) a completely
> relocatable host SDK, by changing the RPATH from an absolute path to
> '$ORIGIN/../lib'.
>
> '$ORIGIN' here is a literal string encoded in the ELF binary and
> replaced at runtime by the location of the binary. So, a binary
> originally created in /home/foo/buildroot/output/host/usr/bin and run
> from there will expect its libraries in
> /home/foo/buildroot/output/host/usr/lib, but the same binary copied
> and run from /tmp/hostsdk/bin will expect its libraries in
> /tmp/hostsdk/lib.
Have you seen:
http://patchwork.ozlabs.org/patch/494781/
http://patchwork.ozlabs.org/patch/494782/
http://patchwork.ozlabs.org/patch/494783/
http://patchwork.ozlabs.org/patch/494784/
http://patchwork.ozlabs.org/patch/494785/
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-12-11 15:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 14:11 [Buildroot] [RFC] Relocatable host tools Thomas De Schampheleire
2015-12-11 15:28 ` Thomas Petazzoni [this message]
2015-12-11 15:55 ` Thomas De Schampheleire
2015-12-11 15:57 ` Thomas Petazzoni
2015-12-11 17:28 ` Yann E. MORIN
2015-12-11 20:25 ` Thomas De Schampheleire
2015-12-13 15:09 ` Samuel Martin
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=20151211162850.327b9e71@free-electrons.com \
--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