From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Bryan Hundven <bryanhundven@gmail.com>
Cc: musl@lists.openwall.com
Subject: Re: musl-cross toolchains now unusable in Buildroot
Date: Thu, 13 Nov 2014 23:44:42 +0100 [thread overview]
Message-ID: <20141113234442.24ea6eb3@free-electrons.com> (raw)
In-Reply-To: <CAJ+oik0oXJz=qKuquNdOL5UJRWodPVftYsfz4oNm7VpGp-uHJg@mail.gmail.com>
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
next prev parent reply other threads:[~2014-11-13 22:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-09 19:56 Thomas Petazzoni
2014-11-09 20:05 ` Bryan Hundven
2014-11-13 22:44 ` Thomas Petazzoni [this message]
2014-11-11 13:15 ` John Spencer
2014-11-13 22:46 ` Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141113234442.24ea6eb3@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=bryanhundven@gmail.com \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).