From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2] toolchain-external: add a specific check to avoid Angstrom toolchains
Date: Tue, 22 Oct 2013 16:30:25 +0200 [thread overview]
Message-ID: <20131022163025.59769db1@skate> (raw)
In-Reply-To: <87zjq1bcyv.fsf@dell.be.48ers.dk>
Peter, Arnout,
On Tue, 22 Oct 2013 16:24:24 +0200, Peter Korsgaard wrote:
> > Just for my info, how is it possible that we cannot use such an
> > Angstrom toolchain as an external toolchain, but it is possible to use
> > a buildroot-generated one? We can also generate a host dir with loads
> > of libs, and these are perfectly usable as external toolchain, right?
>
> No, we can afaik only reuse a buildroot toolchain if it is "bare",
> E.G. no packages selected.
Yes, absolutely. Ideally, my check for "angstrom" toolchain shouldn't
check for angstrom, but should instead validate that the toolchain is
"pure" (i.e only the C library). Unfortunately, I don't quite see an
easy and reliable way to make sure that the only libraries/headers
provided are the ones of the C library.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2013-10-22 14:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-13 8:28 [Buildroot] [PATCHv2] toolchain-external: add a specific check to avoid Angstrom toolchains Thomas Petazzoni
2013-10-13 10:37 ` Thomas De Schampheleire
2013-10-14 11:23 ` Peter Korsgaard
2013-10-17 16:12 ` Arnout Vandecappelle
2013-10-22 14:24 ` Peter Korsgaard
2013-10-22 14:30 ` Thomas Petazzoni [this message]
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=20131022163025.59769db1@skate \
--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