|
yann@448
|
1 |
# glibc options
|
|
yann@1345
|
2 |
# depends on ! BARE_METAL && ARCH_USE_MMU
|
|
yann@448
|
3 |
|
|
yann@922
|
4 |
config LIBC_glibc
|
|
yann@922
|
5 |
select LIBC_SUPPORT_NPTL
|
|
yann@922
|
6 |
select LIBC_SUPPORT_LINUXTHREADS
|
|
yann@922
|
7 |
help
|
|
yann@922
|
8 |
The de-facto standard for Linux distributions.
|
|
yann@922
|
9 |
Feature-rich, but large... Most usefull for desktop-like systems.
|
|
yann@852
|
10 |
|
|
yann@448
|
11 |
choice
|
|
yann@448
|
12 |
bool
|
|
yann@448
|
13 |
prompt "glibc version"
|
|
yann@1535
|
14 |
# Don't remove next line
|
|
yann@1535
|
15 |
# CT_INSERT_VERSION_BELOW
|
|
yann@448
|
16 |
|
|
yann@1758
|
17 |
config LIBC_GLIBC_V_2_11_1
|
|
yann@1758
|
18 |
bool
|
|
yann@1758
|
19 |
prompt "2.11.1 (EXPERIMENTAL)"
|
|
yann@1758
|
20 |
depends on EXPERIMENTAL
|
|
yann@1758
|
21 |
|
|
yann@1758
|
22 |
config LIBC_GLIBC_V_2_11
|
|
yann@1758
|
23 |
bool
|
|
yann@1758
|
24 |
prompt "2.11 (EXPERIMENTAL)"
|
|
yann@1758
|
25 |
depends on EXPERIMENTAL
|
|
yann@1758
|
26 |
|
|
yann@1625
|
27 |
config LIBC_V_2_10_1
|
|
yann@1625
|
28 |
bool
|
|
yann@1625
|
29 |
prompt "2.10.1 (EXPERIMENTAL)"
|
|
yann@1625
|
30 |
depends on EXPERIMENTAL
|
|
yann@1625
|
31 |
select LIBC_GLIBC_USE_PORTS
|
|
yann@1625
|
32 |
|
|
yann@1534
|
33 |
config LIBC_V_2_9
|
|
yann@448
|
34 |
bool
|
|
yann@1534
|
35 |
prompt "2.9"
|
|
yann@448
|
36 |
|
|
yann@1114
|
37 |
config LIBC_V_2_8
|
|
yann@1114
|
38 |
bool
|
|
yann@1260
|
39 |
prompt "2.8"
|
|
yann@1114
|
40 |
|
|
yann@1534
|
41 |
config LIBC_V_2_7
|
|
yann@1114
|
42 |
bool
|
|
yann@1615
|
43 |
prompt "2.7 (OBSOLETE)"
|
|
yann@1615
|
44 |
depends on OBSOLETE
|
|
yann@1534
|
45 |
|
|
yann@1534
|
46 |
config LIBC_V_2_6_1
|
|
yann@1534
|
47 |
bool
|
|
yann@1615
|
48 |
prompt "2.6.1 (OBSOLETE)"
|
|
yann@1615
|
49 |
depends on OBSOLETE
|
|
yann@1534
|
50 |
|
|
yann@1534
|
51 |
config LIBC_V_2_6
|
|
yann@1534
|
52 |
bool
|
|
yann@1615
|
53 |
prompt "2.6 (OBSOLETE)"
|
|
yann@1615
|
54 |
depends on OBSOLETE
|
|
yann@1534
|
55 |
|
|
yann@1534
|
56 |
config LIBC_V_2_5_1
|
|
yann@1534
|
57 |
bool
|
|
yann@1615
|
58 |
prompt "2.5.1 (OBSOLETE)"
|
|
yann@1615
|
59 |
depends on OBSOLETE
|
|
yann@1534
|
60 |
|
|
yann@1534
|
61 |
config LIBC_V_2_5
|
|
yann@1534
|
62 |
bool
|
|
yann@1615
|
63 |
prompt "2.5 (OBSOLETE)"
|
|
yann@1615
|
64 |
depends on OBSOLETE
|
|
yann@1534
|
65 |
|
|
yann@1534
|
66 |
config LIBC_V_2_3_6
|
|
yann@1534
|
67 |
bool
|
|
yann@1534
|
68 |
prompt "2.3.6 (OBSOLETE)"
|
|
yann@1534
|
69 |
depends on OBSOLETE
|
|
yann@1114
|
70 |
|
|
yann@448
|
71 |
endchoice
|
|
yann@448
|
72 |
|
|
yann@448
|
73 |
config LIBC_VERSION
|
|
yann@448
|
74 |
string
|
|
yann@1535
|
75 |
# Don't remove next line
|
|
yann@1535
|
76 |
# CT_INSERT_VERSION_STRING_BELOW
|
|
yann@1758
|
77 |
default "2.11.1" if LIBC_GLIBC_V_2_11_1
|
|
yann@1758
|
78 |
default "2.11" if LIBC_GLIBC_V_2_11
|
|
yann@1625
|
79 |
default "2.10.1" if LIBC_V_2_10_1
|
|
yann@1534
|
80 |
default "2.9" if LIBC_V_2_9
|
|
yann@1534
|
81 |
default "2.8" if LIBC_V_2_8
|
|
yann@1534
|
82 |
default "2.7" if LIBC_V_2_7
|
|
yann@1534
|
83 |
default "2.6.1" if LIBC_V_2_6_1
|
|
yann@1534
|
84 |
default "2.6" if LIBC_V_2_6
|
|
yann@1534
|
85 |
default "2.5.1" if LIBC_V_2_5_1
|
|
yann@1534
|
86 |
default "2.5" if LIBC_V_2_5
|
|
yann@448
|
87 |
default "2.3.6" if LIBC_V_2_3_6
|
|
yann@448
|
88 |
|
|
yann@1260
|
89 |
choice
|
|
yann@1114
|
90 |
bool
|
|
yann@1260
|
91 |
prompt "Retrieval method"
|
|
yann@1260
|
92 |
default LIBC_GLIBC_TARBALL
|
|
yann@1114
|
93 |
|
|
yann@1260
|
94 |
config LIBC_GLIBC_TARBALL
|
|
yann@1260
|
95 |
bool
|
|
yann@1260
|
96 |
prompt "Released tarball"
|
|
yann@1260
|
97 |
help
|
|
yann@1260
|
98 |
Until end of Februrary 2009, there was no tarball for glibc releases
|
|
yann@1260
|
99 |
2.8 and later. This was intentional.
|
|
yann@1260
|
100 |
|
|
yann@1260
|
101 |
Then, all of a sudden, tarballs for those releases have appeared at the
|
|
yann@1260
|
102 |
traditional download place (ftp.gnu.org).
|
|
yann@1260
|
103 |
|
|
yann@1260
|
104 |
Some of the glibc people argue that fixes are committed to the maintenance
|
|
yann@1260
|
105 |
branch, and thus it is the best plac e to retrieve the glibc from.
|
|
yann@1260
|
106 |
On the other hand, it might be preferable to always generate a toolchain
|
|
yann@1260
|
107 |
using a known code-base, so the toolchain can be reproducible.
|
|
yann@1260
|
108 |
|
|
yann@1260
|
109 |
For version prior to 2.8, tarballs were readily available.
|
|
yann@1260
|
110 |
|
|
yann@1260
|
111 |
If you want your toolchain to really be reproducible, say 'Y' here.
|
|
yann@1260
|
112 |
If you can live with a moving code-base, look at the other choice
|
|
yann@1260
|
113 |
entries, below.
|
|
yann@1114
|
114 |
|
|
yann@1260
|
115 |
endchoice
|