# HG changeset patch
# User David Holsgrove <david.holsgrove@xilinx.com>
# Date 1349930265 -36000
# Node ID 24c8bae2216f3223064d16cbf7cd85a3931a0e31
# Parent  0680e81009bedf1329bfcc0a7fb06acbca857963
libc/glibc: Remove redundant LIBC_GLIBC_TARBALL config option

Unused since January 2010.

Signed-off-by: "David Holsgrove" <david.holsgrove@xilinx.com>
Message-Id: <7a666ba8c0ea5e8f4b18.1349931190@localhost.localdomain>
PatchWork-Id: 190783

diff -r 0680e81009be -r 24c8bae2216f config/libc/glibc.in
--- a/config/libc/glibc.in	Thu Oct 11 16:11:35 2012 +0200
+++ b/config/libc/glibc.in	Thu Oct 11 14:37:45 2012 +1000
@@ -9,34 +9,6 @@
 
 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"
 # Don't remove next line
 # CT_INSERT_VERSION_BELOW