From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain: improve musl check to support static toolchains
Date: Fri, 13 Jul 2018 09:23:12 +0200 [thread overview]
Message-ID: <87efg7vbtr.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180707115617.GA2507@scaer> (Yann E. MORIN's message of "Sat, 7 Jul 2018 13:56:17 +0200")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
>> Well, the most obvious indicator is the output of gcc -dumpmachine... Is there
>> any reason why we wouldn't be able to treat that as reliable? AFAIU, hundreds of
>> autotools package will fail if the dumpmachine tuple is not something sane...
> Does that still output the correct tupple for multilib toolchains?
> For example, the mips-2016.05-8-mips-linux-gnu-i686-pc-linux-gnu.tar.bz2
> toolchain is a big-multi-lib toolchain, with both glibc and uclibc, but
> it always returns mips-linux-gnu, even when either is explicitly
> requested:
> $ ./mips-2016.05/bin/mips-linux-gnu-gcc -dumpmachine
> mips-linux-gnu
> $ ./mips-2016.05/bin/mips-linux-gnu-gcc -mglibc -dumpmachine
> mips-linux-gnu
> $ ./mips-2016.05/bin/mips-linux-gnu-gcc -muclibc -dumpmachine
> mips-linux-gnu
> So that unfortunately does not work... :-(
*Grumble* It looked so nice and simple :/
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-07-13 7:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 21:42 [Buildroot] [PATCH] toolchain: improve musl check to support static toolchains Thomas Petazzoni
2018-07-05 2:54 ` Baruch Siach
2018-07-05 7:58 ` Thomas Petazzoni
2018-07-05 22:25 ` Arnout Vandecappelle
2018-07-06 7:36 ` Thomas Petazzoni
2018-07-07 11:56 ` Yann E. MORIN
2018-07-13 7:23 ` Peter Korsgaard [this message]
2018-07-16 22:11 ` Arnout Vandecappelle
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=87efg7vbtr.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox