From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/6494 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:44:42 +0100 Organization: Free Electrons Message-ID: <20141113234442.24ea6eb3@free-electrons.com> References: <20141109205615.737a17a3@free-electrons.com> 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 1415918701 13026 80.91.229.3 (13 Nov 2014 22:45:01 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 13 Nov 2014 22:45:01 +0000 (UTC) Cc: musl@lists.openwall.com To: Bryan Hundven Original-X-From: musl-return-6507-gllmg-musl=m.gmane.org@lists.openwall.com Thu Nov 13 23:44:57 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 1Xp38K-0003cb-VP for gllmg-musl@m.gmane.org; Thu, 13 Nov 2014 23:44:57 +0100 Original-Received: (qmail 28584 invoked by uid 550); 13 Nov 2014 22:44:55 -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 28576 invoked from network); 13 Nov 2014 22:44:55 -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: 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:6494 Archived-At: Dear Bryan Hundven, On Sun, 9 Nov 2014 12:05:23 -0800, Bryan Hundven 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. > > musl-cross uses a config.sh to configure the toolchain settings: > https://bitbucket.org/GregorR/musl-cross/src/tip/config.sh?at=default > > That is where you would set: > ``` > WITH_SYSROOT=yes > ``` > > So, musl-cross does still have sysroot, it just doesn't have it on by default. > Sysroot support does have a problem with the path, which is described > with this bug and patch: > https://bitbucket.org/GregorR/musl-cross/issue/2/sysroot-configuration-bug This is of zero interest for Buildroot. In Buildroot, we have two mechanisms for toolchains: * What we call the "internal toolchain backend", where Buildroot builds its own toolchain. This already has the capability of building musl toolchains, and is completely independent from musl-cross (except from the fact that we borrowed the gcc patches). However, this "backend" forces the user to wait a fairly long time for the toolchain to build. * What we call the "external toolchain backend", where Buildroot simply downloads and uses an already existing pre-built toolchain. This is where the toolchains produced by musl-cross and available at https://e82b27f594c813a5a4ea5b07b06f16c3777c3b8c.googledrive.com/host/0BwnS5DMB0YQ6bDhPZkpOYVFhbk0/ are nice, because Buildroot simply toolchains the tarball, extracts it and voila, we have a working Musl toolchain in a few seconds. So, the fact that musl-cross *allows* to build sysroot-enabled toolchain is of no use to us, if the toolchain proposed by musl-cross at https://e82b27f594c813a5a4ea5b07b06f16c3777c3b8c.googledrive.com/host/0BwnS5DMB0YQ6bDhPZkpOYVFhbk0/ don't have this option enabled. Best regards, Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com