From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] toolchain: allow crosstool-ng musl toolchains
Date: Wed, 29 Jun 2016 17:01:59 +0200 [thread overview]
Message-ID: <20160629170159.17cf9769@free-electrons.com> (raw)
In-Reply-To: <CA+-urNSsOA8bDca-JyW7fZrLcAKWvkVpQaSqobrzD=CqOD2t_g@mail.gmail.com>
Hello,
On Wed, 29 Jun 2016 10:45:32 -0400, Frank Hunleth wrote:
> > Thanks for this patch. However, I dislike a bit this test: the test
> > that libm exists is not super great, and we're really looking at
> > consequences of having musl, and not whether we're using musl or not.
>
> I completely agree. The original test didn't seem like the best test
> for musl, and I like your idea of verifying the linkage of a short C
> program.
>
> I'm quite busy at the moment, but as soon as I free up, I'll play
> around with it and post a revision.
Great, thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-06-29 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 17:36 [Buildroot] [PATCH 1/1] toolchain: allow crosstool-ng musl toolchains Frank Hunleth
2016-06-28 16:24 ` Thomas Petazzoni
2016-06-29 14:45 ` Frank Hunleth
2016-06-29 15:01 ` Thomas Petazzoni [this message]
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=20160629170159.17cf9769@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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