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
17 config LIBC_GLIBC_V_2_11_1
19 prompt "2.11.1 (EXPERIMENTAL)"
20 depends on EXPERIMENTAL
22 config LIBC_GLIBC_V_2_11
24 prompt "2.11 (EXPERIMENTAL)"
25 depends on EXPERIMENTAL
29 prompt "2.10.1 (EXPERIMENTAL)"
30 depends on EXPERIMENTAL
31 select LIBC_GLIBC_USE_PORTS
43 prompt "2.7 (OBSOLETE)"
48 prompt "2.6.1 (OBSOLETE)"
53 prompt "2.6 (OBSOLETE)"
58 prompt "2.5.1 (OBSOLETE)"
63 prompt "2.5 (OBSOLETE)"
68 prompt "2.3.6 (OBSOLETE)"
75 # Don't remove next line
76 # CT_INSERT_VERSION_STRING_BELOW
77 default "2.11.1" if LIBC_GLIBC_V_2_11_1
78 default "2.11" if LIBC_GLIBC_V_2_11
79 default "2.10.1" if LIBC_V_2_10_1
80 default "2.9" if LIBC_V_2_9
81 default "2.8" if LIBC_V_2_8
82 default "2.7" if LIBC_V_2_7
83 default "2.6.1" if LIBC_V_2_6_1
84 default "2.6" if LIBC_V_2_6
85 default "2.5.1" if LIBC_V_2_5_1
86 default "2.5" if LIBC_V_2_5
87 default "2.3.6" if LIBC_V_2_3_6
91 prompt "Retrieval method"
92 default LIBC_GLIBC_TARBALL
94 config LIBC_GLIBC_TARBALL
96 prompt "Released tarball"
98 Until end of Februrary 2009, there was no tarball for glibc releases
99 2.8 and later. This was intentional.
101 Then, all of a sudden, tarballs for those releases have appeared at the
102 traditional download place (ftp.gnu.org).
104 Some of the glibc people argue that fixes are committed to the maintenance
105 branch, and thus it is the best plac e to retrieve the glibc from.
106 On the other hand, it might be preferable to always generate a toolchain
107 using a known code-base, so the toolchain can be reproducible.
109 For version prior to 2.8, tarballs were readily available.
111 If you want your toolchain to really be reproducible, say 'Y' here.
112 If you can live with a moving code-base, look at the other choice