From patchwork Thu Oct 11 04:53:10 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [01, of, 13] libc/glibc: Remove redundant LIBC_GLIBC_TARBALL config option Date: Wed, 10 Oct 2012 18:53:10 -0000 From: David Holsgrove X-Patchwork-Id: 190783 Message-Id: <7a666ba8c0ea5e8f4b18.1349931190@localhost.localdomain> To: yann.morin.1998@free.fr Cc: crossgcc@sourceware.org # HG changeset patch # User David Holsgrove # Date 1349930265 -36000 # Node ID 7a666ba8c0ea5e8f4b18f3c34a8a5bbb170f0233 # Parent 3bc371c2881fe2179808a0ebaceb1cbe4d8215bd libc/glibc: Remove redundant LIBC_GLIBC_TARBALL config option Unused since January 2010. Signed-off-by: "David Holsgrove" --- For unsubscribe information see http://sourceware.org/lists.html#faq diff -r 3bc371c2881f -r 7a666ba8c0ea config/libc/glibc.in --- a/config/libc/glibc.in Sun Oct 07 23:15:57 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