summaryrefslogtreecommitdiff
path: root/config/libc/glibc.in
diff options
context:
space:
mode:
Diffstat (limited to 'config/libc/glibc.in')
-rw-r--r--config/libc/glibc.in73
1 files changed, 46 insertions, 27 deletions
diff --git a/config/libc/glibc.in b/config/libc/glibc.in
index 0f6f2d6..ac35f9d 100644
--- a/config/libc/glibc.in
+++ b/config/libc/glibc.in
@@ -38,13 +38,11 @@ config LIBC_V_2_7
config LIBC_V_2_8
bool
- prompt "2_8"
- select LIBC_GLIBC_2_8_or_later
+ prompt "2.8"
config LIBC_V_2_9
bool
- prompt "2_9"
- select LIBC_GLIBC_2_8_or_later
+ prompt "2.9"
# CT_INSERT_VERSION_ABOVE
# Don't remove above line!
@@ -72,28 +70,48 @@ config LIBC_VERSION
default "2.6" if LIBC_V_2_6
default "2.6.1" if LIBC_V_2_6_1
default "2.7" if LIBC_V_2_7
- default "2_8" if LIBC_V_2_8
- default "2_9" if LIBC_V_2_9
+ default "2.8" if LIBC_V_2_8
+ default "2.9" if LIBC_V_2_9
# CT_INSERT_VERSION_STRING_ABOVE
# Don't remove above line!
-config LIBC_GLIBC_2_8_or_later
+choice
bool
- default n
-
-if LIBC_GLIBC_2_8_or_later
+ prompt "Retrieval method"
+ default LIBC_GLIBC_TARBALL
-config LIBC_GLIBC_latest_snapshot
+config LIBC_GLIBC_TARBALL
bool
- prompt "Use latest nightly snapshot"
- default n
+ prompt "Released tarball"
help
- Say 'y' to use the latest nightly snapshot.
- Not recommended, as the toolchain will not be reproducible.
-
-if ! LIBC_GLIBC_latest_snapshot
+ 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.
+
+config LIBC_GLIBC_CVS
+ bool
+ prompt "CVS checkout"
+ help
+ See the help for the entry "Released tarball", above.
+
+ If you can live with a moving code-base, say 'Y' here.
+ If you want your toolchain to really be reproducible, look at the
+ choice entry "Released tarball from FTP", above.
-comment "Using CVS checkout"
+if LIBC_GLIBC_CVS
config LIBC_GLIBC_CVS_date
string
@@ -102,15 +120,16 @@ config LIBC_GLIBC_CVS_date
help
The date, in ISO-8601 format, at which to check out the repository.
-#config LIBC_GLIBC_CVS_CHECKOUT
+endif # LIBC_GLIBC_CVS
+
+#config LIBC_GLIBC_SNAPSHOT
# bool
-# prompt "checkout instead of export"
-# default n
+# prompt "Use latest nightly snapshot"
# help
-# Use checkout rather than export, so that you can later update
-# the sources.
-# Not recommended, as the toolchain could be non-reproducible.
+# See the help for the entry "Released tarball", above.
+#
+# If you can live with a moving code-base, say 'Y' here.
+# If you want your toolchain to really be reproducible, look at the
+# choice entry "Released tarball from FTP", above.
-endif # ! LIBC_GLIBC_latest_snapshot
-
-endif # LIBC_GLIBC_2_8_or_later
+endchoice