2 # depends on ! BARE_METAL && ARCH_USE_MMU
5 select LIBC_SUPPORT_NPTL
6 select LIBC_SUPPORT_LINUXTHREADS
8 The de-facto standard for Linux distributions.
9 Feature-rich, but large... Most usefull for desktop-like systems.
13 prompt "glibc version"
14 # Don't remove next line
15 # CT_INSERT_VERSION_BELOW
19 prompt "2.10.1 (EXPERIMENTAL)"
20 depends on EXPERIMENTAL
21 select LIBC_GLIBC_USE_PORTS
26 select LIBC_GLIBC_2_8_or_later
31 select LIBC_GLIBC_2_8_or_later
35 prompt "2.7 (OBSOLETE)"
40 prompt "2.6.1 (OBSOLETE)"
45 prompt "2.6 (OBSOLETE)"
50 prompt "2.5.1 (OBSOLETE)"
55 prompt "2.5 (OBSOLETE)"
60 prompt "2.3.6 (OBSOLETE)"
67 # Don't remove next line
68 # CT_INSERT_VERSION_STRING_BELOW
69 default "2.10.1" if LIBC_V_2_10_1
70 default "2.9" if LIBC_V_2_9
71 default "2.8" if LIBC_V_2_8
72 default "2.7" if LIBC_V_2_7
73 default "2.6.1" if LIBC_V_2_6_1
74 default "2.6" if LIBC_V_2_6
75 default "2.5.1" if LIBC_V_2_5_1
76 default "2.5" if LIBC_V_2_5
77 default "2.3.6" if LIBC_V_2_3_6
79 config LIBC_GLIBC_2_8_or_later
85 prompt "Retrieval method"
86 default LIBC_GLIBC_TARBALL
88 config LIBC_GLIBC_TARBALL
90 prompt "Released tarball"
91 depends on ! LIBC_GLIBC_2_8_or_later || ! ( LIBC_GLIBC_USE_PORTS || ( LIBC_ADDONS_LIST != "" ) )
93 Until end of Februrary 2009, there was no tarball for glibc releases
94 2.8 and later. This was intentional.
96 Then, all of a sudden, tarballs for those releases have appeared at the
97 traditional download place (ftp.gnu.org).
99 Some of the glibc people argue that fixes are committed to the maintenance
100 branch, and thus it is the best plac e to retrieve the glibc from.
101 On the other hand, it might be preferable to always generate a toolchain
102 using a known code-base, so the toolchain can be reproducible.
104 For version prior to 2.8, tarballs were readily available.
106 If you want your toolchain to really be reproducible, say 'Y' here.
107 If you can live with a moving code-base, look at the other choice
110 config LIBC_GLIBC_CVS
112 prompt "CVS checkout"
114 See the help for the entry "Released tarball", above.
116 If you can live with a moving code-base, say 'Y' here.
117 If you want your toolchain to really be reproducible, look at the
118 choice entry "Released tarball from FTP", above.
122 config LIBC_GLIBC_CVS_date
124 prompt "checkout as of date"
127 The date, in ISO-8601 format, at which to check out the repository.
129 endif # LIBC_GLIBC_CVS