From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/6495 Path: news.gmane.org!not-for-mail From: Thomas Petazzoni Newsgroups: gmane.linux.lib.musl.general Subject: Re: musl-cross toolchains now unusable in Buildroot Date: Thu, 13 Nov 2014 23:46:10 +0100 Organization: Free Electrons Message-ID: <20141113234610.524e0d14@free-electrons.com> References: <20141109205615.737a17a3@free-electrons.com> <54620C00.8000507@barfooze.de> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1415918790 14552 80.91.229.3 (13 Nov 2014 22:46:30 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 13 Nov 2014 22:46:30 +0000 (UTC) Cc: musl@lists.openwall.com To: John Spencer Original-X-From: musl-return-6508-gllmg-musl=m.gmane.org@lists.openwall.com Thu Nov 13 23:46:26 2014 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1Xp39l-0004Db-Po for gllmg-musl@m.gmane.org; Thu, 13 Nov 2014 23:46:25 +0100 Original-Received: (qmail 30227 invoked by uid 550); 13 Nov 2014 22:46:23 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 30218 invoked from network); 13 Nov 2014 22:46:23 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mail.free-electrons.com X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,SHORTCIRCUIT, URIBL_BLOCKED shortcircuit=ham autolearn=disabled version=3.4.0 In-Reply-To: <54620C00.8000507@barfooze.de> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; x86_64-pc-linux-gnu) Xref: news.gmane.org gmane.linux.lib.musl.general:6495 Archived-At: 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 > > 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 > > directory, which normally contains files such as > > . This is for example causing a problem as > > Buildroot checks the kernel headers version using , > > 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 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 https://bitbucket.org/GregorR/musl-cross/issue/6/non-standard-kernel-headers-causing-issues, but his reply was not very clear (at least not clear to me). Best regards, Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com