yann@922
|
1 |
# This file contains the common configuration options
|
yann@922
|
2 |
# that apply to both glibc and eglibc.
|
yann@922
|
3 |
|
yann@922
|
4 |
comment "glibc/eglibc common options"
|
yann@922
|
5 |
|
yann@922
|
6 |
config LIBC_GLIBC_EXTRA_CONFIG
|
yann@922
|
7 |
string
|
yann@922
|
8 |
prompt "extra config"
|
yann@922
|
9 |
default ""
|
yann@922
|
10 |
help
|
yann@922
|
11 |
Extra flags to pass onto ./configure when configuring.
|
yann@922
|
12 |
|
yann@922
|
13 |
Eg.: --enable-static-nss
|
yann@922
|
14 |
|
yann@922
|
15 |
config LIBC_GLIBC_EXTRA_CFLAGS
|
yann@922
|
16 |
string
|
yann@922
|
17 |
prompt "extra target CFLAGS"
|
yann@922
|
18 |
default ""
|
yann@922
|
19 |
help
|
yann@922
|
20 |
Extra target CFLAGS to use when building.
|
yann@922
|
21 |
|
yann@922
|
22 |
config LIBC_EXTRA_CC_ARGS
|
yann@922
|
23 |
string
|
yann@922
|
24 |
prompt "gcc extra flags"
|
yann@922
|
25 |
default ""
|
yann@922
|
26 |
help
|
yann@922
|
27 |
Extra flags to pass gcc when building.
|
yann@922
|
28 |
|
yann@922
|
29 |
Seldom used, except for sparc64 which seems to need the flag -64
|
yann@922
|
30 |
to be passed onto gcc.
|
yann@922
|
31 |
|
yann@922
|
32 |
config LIBC_GLIBC_USE_PORTS
|
yann@922
|
33 |
bool
|
yann@922
|
34 |
prompt "Use the ports addon"
|
yann@922
|
35 |
default n
|
yann@922
|
36 |
help
|
yann@922
|
37 |
The ports addon contains some architecture ports that are not available
|
yann@922
|
38 |
in the official distribution.
|
yann@922
|
39 |
|
yann@922
|
40 |
For example, this is the case for ARM with for 2.4 and above.
|
yann@922
|
41 |
|
yann@922
|
42 |
Say n only if you're sure that your architecture is in the official
|
yann@922
|
43 |
distribution for your chosen version.
|
yann@922
|
44 |
|
yann@922
|
45 |
config LIBC_ADDONS_LIST
|
yann@922
|
46 |
string
|
yann@922
|
47 |
prompt "Extra addons"
|
yann@922
|
48 |
default ""
|
yann@922
|
49 |
help
|
yann@922
|
50 |
Extra addons to include. Space separated list.
|
yann@922
|
51 |
|
yann@922
|
52 |
You need to specify neither linuxthreads nor nptl, as they are added
|
yann@922
|
53 |
automagically for you depending on the threading model you choosed
|
yann@922
|
54 |
earlier.
|
yann@922
|
55 |
|
yann@922
|
56 |
Eg.: crypt (for very old libces)
|
yann@922
|
57 |
|
yann@922
|
58 |
if KERNEL_linux
|
yann@922
|
59 |
|
yann@922
|
60 |
choice
|
yann@922
|
61 |
bool
|
yann@922
|
62 |
prompt "Minimum supported kernel version"
|
yann@922
|
63 |
default LIBC_GLIBC_KERNEL_VERSION_AS_HEADERS
|
yann@922
|
64 |
|
yann@922
|
65 |
config LIBC_GLIBC_KERNEL_VERSION_NONE
|
yann@922
|
66 |
bool
|
yann@922
|
67 |
prompt "Let ./configure decide"
|
yann@922
|
68 |
help
|
yann@922
|
69 |
Let ./configure decide what minimum kernel version glibc/eglibc
|
yann@922
|
70 |
will be able to run against.
|
yann@922
|
71 |
|
yann@922
|
72 |
This will inclde legacy compatibility code for older kernels in
|
yann@922
|
73 |
the C library, thus ensuring that it will run on a large number
|
yann@922
|
74 |
of old kernels.
|
yann@922
|
75 |
|
yann@922
|
76 |
The minimum kernel version supported will be dependent upon the
|
yann@922
|
77 |
target you build for. For example:
|
yann@922
|
78 |
alpha*-*-linux-gnu Requires Linux 2.6.9 for NPTL
|
yann@922
|
79 |
sh[34]-*-linux-gnu Requires Linux 2.6.11
|
yann@922
|
80 |
powerpc* Requires Linux 2.4.19
|
yann@922
|
81 |
arm*-*-linux-*gnueabi Requires Linux 2.6.16
|
yann@922
|
82 |
|
yann@922
|
83 |
config LIBC_GLIBC_KERNEL_VERSION_AS_HEADERS
|
yann@922
|
84 |
bool
|
yann@922
|
85 |
prompt "Same as kernel headers (default)"
|
yann@922
|
86 |
help
|
yann@922
|
87 |
Normaly, you'll want glibc/eglibc to run against the same kernel
|
yann@922
|
88 |
version as the one used for the headers.
|
yann@922
|
89 |
|
yann@922
|
90 |
This is the default.
|
yann@922
|
91 |
|
yann@922
|
92 |
If enabled, crosstool-ng will use the chosen version of kernel
|
yann@922
|
93 |
headers for the glibc minimum kernel version supported, which is
|
yann@922
|
94 |
what gets passed to "--enable-kernel=" when configuring glibc.
|
yann@922
|
95 |
|
yann@922
|
96 |
Enabling this will ensure that no legacy compatibility code for
|
yann@922
|
97 |
older kernels is built into your C libraries, but it will
|
yann@922
|
98 |
be unable to run on kernel versions older than whichever kernel
|
yann@922
|
99 |
headers version you've built the toolchain for.
|
yann@922
|
100 |
|
yann@922
|
101 |
If you know for sure that your toolchain will never need to build
|
yann@922
|
102 |
applications that will run under a kernel version older than your
|
yann@922
|
103 |
chosen kernel headers version (CT_KERNEL_VERSION), you can choose
|
yann@922
|
104 |
"y" here.
|
yann@922
|
105 |
|
yann@922
|
106 |
config LIBC_GLIBC_KERNEL_VERSION_CHOSEN
|
yann@922
|
107 |
bool
|
yann@922
|
108 |
prompt "Specific kernel version"
|
yann@922
|
109 |
help
|
yann@922
|
110 |
Specify the earliest Linux kernel version you want glibc to
|
yann@922
|
111 |
include support for. This does not have to match the kernel
|
yann@922
|
112 |
headers version used for your toolchain. This controls what is
|
yann@922
|
113 |
passed to the "--enable-kernel=" option to the glibc configure
|
yann@922
|
114 |
script.
|
yann@922
|
115 |
|
yann@922
|
116 |
If you want to be able to statically link programs with your
|
yann@922
|
117 |
toolchain's C library, make sure this kernel version is lower than
|
yann@922
|
118 |
all kernels you wish to support to avoid "FATAL: kernel too old"
|
yann@922
|
119 |
errors. The higher the version you specify, the less legacy code
|
yann@922
|
120 |
will be built into libc.
|
yann@922
|
121 |
|
yann@922
|
122 |
Most people can leave this at the default value of "2.6.9".
|
yann@922
|
123 |
|
yann@922
|
124 |
if LIBC_GLIBC_KERNEL_VERSION_CHOSEN
|
yann@922
|
125 |
|
yann@922
|
126 |
config LIBC_GLIBC_MIN_KERNEL_VERSION
|
yann@922
|
127 |
string
|
yann@922
|
128 |
prompt "Minimum kernel version to support"
|
yann@922
|
129 |
default "2.6.9"
|
yann@922
|
130 |
help
|
yann@922
|
131 |
Enter here the lowest kernel version glibc/eglibc will be able to
|
yann@922
|
132 |
run against.
|
yann@922
|
133 |
|
yann@922
|
134 |
The minimum kernel version supported will be dependent upon the
|
yann@922
|
135 |
target you build for. For example:
|
yann@922
|
136 |
alpha*-*-linux-gnu Requires Linux 2.6.9 for NPTL
|
yann@922
|
137 |
sh[34]-*-linux-gnu Requires Linux 2.6.11
|
yann@922
|
138 |
powerpc* Requires Linux 2.4.19
|
yann@922
|
139 |
arm*-*-linux-*gnueabi Requires Linux 2.6.16
|
yann@922
|
140 |
|
yann@922
|
141 |
Note that no sanity check is performed by crosstool-NG to ensure
|
yann@922
|
142 |
that the value you enter here is appropriate for your target.
|
yann@922
|
143 |
|
yann@922
|
144 |
endif # LIBC_GLIBC_KERNEL_VERSION_CHOSEN
|
yann@922
|
145 |
|
yann@922
|
146 |
endchoice
|
yann@922
|
147 |
|
yann@922
|
148 |
config LIBC_GLIBC_MIN_KERNEL
|
yann@922
|
149 |
string
|
yann@922
|
150 |
default "" if LIBC_GLIBC_KERNEL_VERSION_NONE
|
yann@922
|
151 |
default KERNEL_VERSION if LIBC_GLIBC_KERNEL_VERSION_AS_HEADERS
|
yann@922
|
152 |
default LIBC_GLIBC_MIN_KERNEL_VERSION if LIBC_GLIBC_USE_HEADERS_MIN_KERNEL
|
yann@922
|
153 |
|
yann@922
|
154 |
endif # KERNEL_linux
|