From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] external-toolchain: BR2_TOOLCHAIN_EXTERNAL_GLIBC includes eglibc
Date: Tue, 25 Sep 2012 09:54:42 +0200 [thread overview]
Message-ID: <20120925095442.01c07b54@skate> (raw)
In-Reply-To: <1348544993-5682-1-git-send-email-baruch@tkos.co.il>
Dear Baruch Siach,
On Tue, 25 Sep 2012 05:49:53 +0200, Baruch Siach wrote:
> + Note: eglibc is a variant of glibc that (among other things) can be
> + configured to exclude parts of its features. This capability is
> + currently not supported.
This note makes no sense in the context of external toolchains: the C
library is already compiled into the external toolchain, so it's the
responsibility of the person building the external toolchain to know
how to configure eglibc. The fact that we don't support eglibc
configuration in Buildroot doesn't make much sense.
Or, if you want to mean that we don't support eglibc toolchains that
have been configured to leave out certain features (such as IPv6
support for example), then it should be said in a different way, such
as: "We only support eglibc toolchains providing this, that and this
other feature".
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-09-25 7:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 3:49 [Buildroot] [PATCH] external-toolchain: BR2_TOOLCHAIN_EXTERNAL_GLIBC includes eglibc Baruch Siach
2012-09-25 7:54 ` Thomas Petazzoni [this message]
2012-09-25 8:33 ` Baruch Siach
2012-09-25 8:39 ` Thomas Petazzoni
2012-09-25 13:46 ` Baruch Siach
-- strict thread matches above, loose matches on Subject: below --
2012-09-24 19:38 Baruch Siach
2012-09-24 20:26 ` Yann E. MORIN
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=20120925095442.01c07b54@skate \
--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