[Buildroot] [PATCH v4 04/22] toolchain-external: introduce toolchain-external-package

[Thomas Petazzoni <thomas.petazzoni@free-electrons.com>]

Hello,

On Tue, 8 Nov 2016 13:30:16 +0100, Arnout Vandecappelle wrote:

>  That would be useful if such a toolchain uncovers problems that we can fix in
> Buildroot. If all it does is to add autobuilder exceptions, there isn't much
> point... Well, the other thing we can do is to add *_AT_LEAST_NNN options,
> that's true.

Yes, that's what I'm thinking of: it allows us to realize when a
package needs gcc 4.7 or 4.8, or when some fairly recent kernel headers
are needed, for example. If all we test is gcc 4.9 with 4.0 kernel
headers, then all our users that are stuck with 4.7 (or older
toolchains) with 3.0 kernel headers will have a really bad experience.

>  Those autobuilder exceptions for ct-ng, what kind of errors are they for? Not
> something covered by *_AT_LEAST? Like bugs in libc, for which we don't have
> _AT_LEAST?

Looking quickly at the autobuild-run exceptions, we have:

 - Toolchains with gcc affected by various PRs

 - Toolchains with too old eglibc (2.18)

 - Toolchains that fail to build this or that package, with no
   documented reason (might be explained in the commit log, though).

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