From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain/external: do not accept distro-class toolchains
Date: Tue, 27 Jan 2015 22:16:04 +0100 [thread overview]
Message-ID: <20150127221604.134cffdb@free-electrons.com> (raw)
In-Reply-To: <54C7FF64.3030501@mind.be>
Dear Arnout Vandecappelle,
On Tue, 27 Jan 2015 22:13:08 +0100, Arnout Vandecappelle wrote:
> This sounds as if the problem is that the binary can't be moved to a different
> place. But for pre-installed external toolchains, we don't do that.
>
> But I guess the real problem is that we can't copy the libs to the staging dir,
> right? So perhaps that should be written in this remark.
Yes the problem is more that such toolchains typically don't have a
clean sysroot, with just the C library, C library headers and kernel
headers.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-01-27 21:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-25 22:41 [Buildroot] [PATCH] toolchain/external: do not accept distro-class toolchains Yann E. MORIN
2015-01-27 21:13 ` Arnout Vandecappelle
2015-01-27 21:16 ` Thomas Petazzoni [this message]
2015-01-28 18:34 ` Yann E. MORIN
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=20150127221604.134cffdb@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