From 110027316e7320a6a187436e5a990b1166b06b59 Mon Sep 17 00:00:00 2001 From: David Holsgrove Date: Thu, 11 Oct 2012 14:37:45 +1000 Subject: libc/glibc: Remove redundant LIBC_GLIBC_TARBALL config option Unused since January 2010. Signed-off-by: "David Holsgrove" Message-Id: <7a666ba8c0ea5e8f4b18.1349931190@localhost.localdomain> PatchWork-Id: 190783 --- config/libc/glibc.in | 28 ---------------------------- 1 file changed, 28 deletions(-) (limited to 'config/libc') diff --git a/config/libc/glibc.in b/config/libc/glibc.in index 963fb38a..0cf6287e 100644 --- a/config/libc/glibc.in +++ b/config/libc/glibc.in @@ -7,34 +7,6 @@ ## help The de-facto standard for Linux distributions. ## help Feature-rich, but large... Most usefull for desktop-like systems. -choice - bool - prompt "Retrieval method" - default LIBC_GLIBC_TARBALL - -config LIBC_GLIBC_TARBALL - bool - prompt "Released tarball" - help - Until end of Februrary 2009, there was no tarball for glibc releases - 2.8 and later. This was intentional. - - Then, all of a sudden, tarballs for those releases have appeared at the - traditional download place (ftp.gnu.org). - - Some of the glibc people argue that fixes are committed to the maintenance - branch, and thus it is the best plac e to retrieve the glibc from. - On the other hand, it might be preferable to always generate a toolchain - using a known code-base, so the toolchain can be reproducible. - - For version prior to 2.8, tarballs were readily available. - - If you want your toolchain to really be reproducible, say 'Y' here. - If you can live with a moving code-base, look at the other choice - entries, below. - -endchoice - choice bool prompt "glibc version" -- cgit v1.2.3