1.1 --- a/config/libc/glibc.in Mon Jan 11 22:47:58 2010 +0100
1.2 +++ b/config/libc/glibc.in Wed Jun 09 00:41:25 2010 +0200
1.3 @@ -10,6 +10,34 @@
1.4
1.5 choice
1.6 bool
1.7 + prompt "Retrieval method"
1.8 + default LIBC_GLIBC_TARBALL
1.9 +
1.10 +config LIBC_GLIBC_TARBALL
1.11 + bool
1.12 + prompt "Released tarball"
1.13 + help
1.14 + Until end of Februrary 2009, there was no tarball for glibc releases
1.15 + 2.8 and later. This was intentional.
1.16 +
1.17 + Then, all of a sudden, tarballs for those releases have appeared at the
1.18 + traditional download place (ftp.gnu.org).
1.19 +
1.20 + Some of the glibc people argue that fixes are committed to the maintenance
1.21 + branch, and thus it is the best plac e to retrieve the glibc from.
1.22 + On the other hand, it might be preferable to always generate a toolchain
1.23 + using a known code-base, so the toolchain can be reproducible.
1.24 +
1.25 + For version prior to 2.8, tarballs were readily available.
1.26 +
1.27 + If you want your toolchain to really be reproducible, say 'Y' here.
1.28 + If you can live with a moving code-base, look at the other choice
1.29 + entries, below.
1.30 +
1.31 +endchoice
1.32 +
1.33 +choice
1.34 + bool
1.35 prompt "glibc version"
1.36 # Don't remove next line
1.37 # CT_INSERT_VERSION_BELOW
1.38 @@ -85,31 +113,3 @@
1.39 default "2.5.1" if LIBC_V_2_5_1
1.40 default "2.5" if LIBC_V_2_5
1.41 default "2.3.6" if LIBC_V_2_3_6
1.42 -
1.43 -choice
1.44 - bool
1.45 - prompt "Retrieval method"
1.46 - default LIBC_GLIBC_TARBALL
1.47 -
1.48 -config LIBC_GLIBC_TARBALL
1.49 - bool
1.50 - prompt "Released tarball"
1.51 - help
1.52 - Until end of Februrary 2009, there was no tarball for glibc releases
1.53 - 2.8 and later. This was intentional.
1.54 -
1.55 - Then, all of a sudden, tarballs for those releases have appeared at the
1.56 - traditional download place (ftp.gnu.org).
1.57 -
1.58 - Some of the glibc people argue that fixes are committed to the maintenance
1.59 - branch, and thus it is the best plac e to retrieve the glibc from.
1.60 - On the other hand, it might be preferable to always generate a toolchain
1.61 - using a known code-base, so the toolchain can be reproducible.
1.62 -
1.63 - For version prior to 2.8, tarballs were readily available.
1.64 -
1.65 - If you want your toolchain to really be reproducible, say 'Y' here.
1.66 - If you can live with a moving code-base, look at the other choice
1.67 - entries, below.
1.68 -
1.69 -endchoice