Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Thu, 13 Nov 2014 23:46:10 +0100
From: Thomas Petazzoni <>
To: John Spencer <>
Subject: Re: musl-cross toolchains now unusable in Buildroot

Dear John Spencer,

On Tue, 11 Nov 2014 14:15:44 +0100, John Spencer wrote:

> >  * The toolchains have the sysroot mechanism disabled. For an unknown
> >    reason, in commit
> >,
> >    the sysroot feature was disabled. This is weird, as essentially all
> >    modern toolchains have the sysroot feature enabled. This is
> >    essential for Buildroot to use a pre-built toolchain.
> > 
> >    I've filled
> >
> >    about this issue.
> > 
> >  * The absence of complete kernel headers. I don't know if it's related
> >    to the change to use the sanitized headers from the Sabotage
> >    project, or some other change, but the toolchain no longer has the
> >    <linux/...> directory, which normally contains files such as
> >    <linux/version.h>. This is for example causing a problem as
> >    Buildroot checks the kernel headers version using <linux/version.h>,
> >    though this particular aspect could potentially be fixed.
> > 
> >    I've filled
> >
> >    about this issue.
> there's already an issue filed here

Yes, I know. both issues are duplicated on bitbucket and github, and
it's not clear which of the two places is the official bug tracker for
musl-cross. I asked Gregor about this at,
but his reply was not very clear (at least not clear to me).

Best regards,

Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.