From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v8 08/10] external-toolchain: check if a buildroot SDK has already been relocated
Date: Fri, 21 Jul 2017 10:05:26 +0200 [thread overview]
Message-ID: <20170721100526.7e014194@windsurf> (raw)
In-Reply-To: <5954a27f-ac93-99ee-5216-2cc73b15385b@grandegger.com>
Hello,
On Fri, 21 Jul 2017 09:44:00 +0200, Wolfgang Grandegger wrote:
> > "make sdk" will definitely create just the toolchain if what you have
> > in your configuration is... just the toolchain, which is exactly how I
> > build Buildroot toolchains, such as the ones used by the autobuilders
> > or on toolchains.free-electrons.com.
> >
> > Doing "make toolchain" doesn't work for this use case, because you
> > definitely want the RPATH sanitization of host binaries done in "make
> > sdk".
> >
> > Again, I think this additional check in the external toolchain code is
> > useless. For a SDK to be usable as an external toolchain, it has to be
> > a SDK that contains *just* a toolchain and *nothing* else. If its
> > sysroot is polluted with additional libraries than the C library, it
> > cannot be used as an external toolchain. And therefore, the
> > relocate-sdk procedure is useless, because there's nothing to relocate
> > in an SDK that is just a toolchain.
>
> OK. I see. Then I will drop this patch.
Let's see if Arnout agrees with my reasoning. Quite often he points me
at details I have missed :-)
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-07-21 8:05 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 14:35 [Buildroot] [PATCH v8 00/10] Make the SDK relocatable Wolfgang Grandegger
2017-07-20 14:35 ` [Buildroot] [PATCH v8 01/10] support/scripts: relocate-sdk.sh now uses a normal pipe to find strings Wolfgang Grandegger
2017-07-20 20:30 ` Thomas Petazzoni
2017-07-20 14:35 ` [Buildroot] [PATCH v8 02/10] package/patchelf: add patch for rpath sanitization under a root directory Wolfgang Grandegger
2017-07-20 20:30 ` Thomas Petazzoni
2017-07-20 14:35 ` [Buildroot] [PATCH v8 03/10] support/scripts: add fix-rpath script to sanitize the rpath Wolfgang Grandegger
2017-07-20 20:49 ` Thomas Petazzoni
2017-07-20 21:05 ` Arnout Vandecappelle
2017-07-20 21:11 ` Thomas Petazzoni
2017-07-21 7:35 ` Wolfgang Grandegger
2017-07-21 7:40 ` Thomas Petazzoni
2017-07-21 7:45 ` Wolfgang Grandegger
2017-07-20 21:03 ` Arnout Vandecappelle
2017-07-20 21:12 ` Thomas Petazzoni
2017-07-20 14:35 ` [Buildroot] [PATCH v8 04/10] patchelf: always build this package required for RPATH sanitization Wolfgang Grandegger
2017-07-20 20:49 ` Thomas Petazzoni
2017-07-20 14:35 ` [Buildroot] [PATCH v8 05/10] core: sanitize RPATH in target tree before copying the overlay Wolfgang Grandegger
2017-07-20 20:49 ` Thomas Petazzoni
2017-07-20 14:35 ` [Buildroot] [PATCH v8 06/10] core: introduce "sdk" target to make a relocatable SDK Wolfgang Grandegger
2017-07-20 21:11 ` Arnout Vandecappelle
2017-07-20 21:18 ` Thomas Petazzoni
2017-07-20 14:35 ` [Buildroot] [PATCH v8 07/10] core: sanitize RPATH in staging tree " Wolfgang Grandegger
2017-07-20 14:35 ` [Buildroot] [PATCH v8 08/10] external-toolchain: check if a buildroot SDK has already been relocated Wolfgang Grandegger
2017-07-20 21:21 ` Thomas Petazzoni
2017-07-20 22:30 ` Arnout Vandecappelle
2017-07-21 6:36 ` Thomas Petazzoni
2017-07-21 6:52 ` Wolfgang Grandegger
2017-07-21 7:24 ` Thomas Petazzoni
2017-07-21 7:44 ` Wolfgang Grandegger
2017-07-21 8:05 ` Thomas Petazzoni [this message]
2017-07-21 20:31 ` Arnout Vandecappelle
2017-07-21 20:40 ` Thomas Petazzoni
2017-07-22 10:49 ` Arnout Vandecappelle
2017-07-20 14:35 ` [Buildroot] [PATCH v8 09/10] core: install relocation script and location to make a relocatable SDK Wolfgang Grandegger
2017-07-20 14:35 ` [Buildroot] [PATCH v8 10/10] package/qt5base: provide "qt.conf" to make "qmake" relocatable Wolfgang Grandegger
2017-07-20 21:03 ` 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=20170721100526.7e014194@windsurf \
--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 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.