Date: Tue, 11 Nov 2014 14:15:44 +0100 From: John Spencer <maillist-musl@...fooze.de> To: musl@...ts.openwall.com Subject: Re: musl-cross toolchains now unusable in Buildroot Thomas Petazzoni wrote: > Hello, > > Since quite a while, we've added support in Buildroot for the pre-built > toolchains provided by musl-cross. This was a great way for people to > test very easily the musl C library, and therefore get more people to > use it. > > We're currently using the 1.1.1 version of the toolchain. > Unfortunately, since version 1.1.2, two things have changed that > prevent us from using the pre-built toolchains: > > * The toolchains have the sysroot mechanism disabled. For an unknown > reason, in commit > https://bitbucket.org/GregorR/musl-cross/commits/f9c0c3c34f0fe122541a129f1aa87686954d5f1b, > 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 > https://bitbucket.org/GregorR/musl-cross/issue/5/sysroot-support-needed-for-buildroot > 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 > https://bitbucket.org/GregorR/musl-cross/issue/6/non-standard-kernel-headers-causing-issues > about this issue. there's already an issue filed here https://github.com/GregorR/musl-cross/issues/30
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.