From: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH for-2013.11] glibc/eglibc: remove reference to experimental from help text
Date: Tue, 19 Nov 2013 09:00:07 +0100 [thread overview]
Message-ID: <1384848007-8853-1-git-send-email-arnout@mind.be> (raw)
Since 924b8739da we no longer declare glibc and eglibc support as
experimental, so it shouldn't be mentioned in the help text anymore.
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
---
toolchain/toolchain-buildroot/Config.in | 6 ------
1 file changed, 6 deletions(-)
diff --git a/toolchain/toolchain-buildroot/Config.in b/toolchain/toolchain-buildroot/Config.in
index 8b37127..81593f1 100644
--- a/toolchain/toolchain-buildroot/Config.in
+++ b/toolchain/toolchain-buildroot/Config.in
@@ -31,9 +31,6 @@ config BR2_TOOLCHAIN_BUILDROOT_EGLIBC
This option selects eglibc as the C library for the
cross-compilation toolchain.
- The eglibc support in the Buildroot toolchain backend is
- very recent, and therefore marked experimental.
-
http://eglibc.org
config BR2_TOOLCHAIN_BUILDROOT_GLIBC
@@ -51,9 +48,6 @@ config BR2_TOOLCHAIN_BUILDROOT_GLIBC
This option selects glibc as the C library for the
cross-compilation toolchain.
- The glibc support in the Buildroot toolchain backend is
- very recent, and therefore marked experimental.
-
http://www.gnu.org/software/libc/
comment "(e)glibc only available with shared lib support"
--
1.8.4.2
next reply other threads:[~2013-11-19 8:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 8:00 Arnout Vandecappelle [this message]
2013-11-19 8:10 ` [Buildroot] [PATCH for-2013.11] glibc/eglibc: remove reference to experimental from help text Thomas Petazzoni
2013-11-19 8:13 ` Peter Korsgaard
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=1384848007-8853-1-git-send-email-arnout@mind.be \
--to=arnout@mind.be \
--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