1 # This file contains the common configuration options
2 # that apply to both glibc and eglibc.
4 # Some architectures require the ports addon. List them one by one here:
5 # This list must be carefully in sync with the architectures names
6 # we can find in config/arch/*
7 config LIBC_GLIBC_MAY_FORCE_PORTS
10 default y if ARCH_mips
11 select LIBC_GLIBC_USE_PORTS
13 # Force using the BFD linker during the toolchain build
14 config LIBC_glibc_familly
17 select BINUTILS_FORCE_LD_BFD
19 config LIBC_GLIBC_EXTRA_CONFIG_ARRAY
24 Extra flags to pass onto ./configure when configuring.
26 You can enter multiple arguments here, and arguments can contain spaces
27 if they are properly quoted (or escaped, but prefer quotes). Eg.:
28 --with-foo="1st arg with 4 spaces" --with-bar=2nd-arg-without-space
30 config LIBC_GLIBC_CONFIGPARMS
32 prompt "Extra config params (READ HELP)"
33 default "" if ! ARCH_sh
34 default "no-z-defs=yes" if ARCH_sh
36 Some architectures need to set options in the file configparms.
37 This is the case for sh3/4, which really need to set configparms
38 to "no-z-defs=yes" as of gcc-3.4/glibc-2.3.2.
40 Unless you are building a toolchain for sh3/4, you should leave that empty.
42 Note: If you need to pass more than one value, separate them with
43 '\n'. Eg.: var1=val1\nvar2=val2
45 config LIBC_GLIBC_EXTRA_CFLAGS
47 prompt "extra target CFLAGS"
50 Extra target CFLAGS to use when building.
52 config LIBC_EXTRA_CC_ARGS
54 prompt "gcc extra flags"
57 Extra flags to pass gcc when building.
59 Seldom used, except for sparc64 which seems to need the flag -64
60 to be passed onto gcc.
62 config LIBC_ENABLE_FORTIFIED_BUILD
64 prompt "Enable fortified build (EXPERIMENTAL)"
65 depends on EXPERIMENTAL
67 If you say 'y' here, then glibc will be using fortified versions
68 of functions with format arguments (eg. vsyslog, printf...), and
69 do a sanity check on the format at runtime, to avoid some of the
70 common format string attacks.
72 This is currently not supported, and will most probably result in
73 a broken build, with an error message like:
74 ../misc/syslog.c: In function '__vsyslog_chk':
75 ../misc/syslog.c:123: sorry, unimplemented: inlining failed in
76 call to 'syslog': function body not available
78 If you are brave enough and want to debug the issue, then say 'y'
79 here. Otherwise, be still and say 'n' (the default). ;-)
82 config LIBC_DISABLE_VERSIONING
84 prompt "Disable symbols versioning"
86 Do not include versioning information in the library objects.
88 config LIBC_OLDEST_ABI
90 prompt "Oldest supported ABI"
93 Set the oldest ABI supported by the C library.
95 Setting this option, for example, to 2.2 will provide ABI support
98 If this option is not set, (e)glibc will choose for you.
100 config LIBC_GLIBC_FORCE_UNWIND
102 prompt "Force unwind support (READ HELP!)"
104 If your toolchain fails building while building the C library
105 start files, or the complete C library, with a message like:
106 configure: error: forced unwind support is required
108 then you may try setting this to 'y'. Otherwise, leave it to 'n'.
110 The issue seems to be related to building NPTL on old versions
111 of glibc (and possibly eglibc as well) on some architectures
112 (seen on s390, s390x and x86_64).
114 config LIBC_GLIBC_USE_PORTS
116 prompt "Use the ports addon"
118 The ports addon contains some architecture ports that are not available
119 in the official distribution.
121 For example, this is the case for ARM with glibc-2.4 and above.
123 Say n only if you're sure that your architecture is in the official
124 distribution for your chosen version.
126 config LIBC_ADDONS_LIST
128 prompt "Extra addons"
131 Extra addons to include. Space separated list.
133 You need to specify neither linuxthreads nor nptl, as they are added
134 automagically for you depending on the threading model you choosed
137 Eg.: crypt (for very old libces)
139 if LIBC_GLIBC_USE_PORTS || ( LIBC_ADDONS_LIST != "" )
140 comment "WARNING !!! "
141 comment "| For glibc >= 2.8, it can happen that the tarballs "
142 comment "| for the addons are not available for download. "
143 comment "| If that happens, bad luck... Try a previous version "
144 comment "| or try again later... :-( "
149 choice LIBC_GLIBC_SUPPORTED_KERNEL
151 prompt "Minimum supported kernel version"
152 default LIBC_GLIBC_KERNEL_VERSION_AS_HEADERS
154 config LIBC_GLIBC_KERNEL_VERSION_NONE
156 prompt "Let ./configure decide"
158 Let ./configure decide what minimum kernel version glibc/eglibc
159 will be able to run against.
161 This will include legacy compatibility code for older kernels in
162 the C library, thus ensuring that it will run on a large number
165 The minimum kernel version supported will be dependent upon the
166 target you build for. For example:
167 alpha*-*-linux-gnu Requires Linux 2.6.9 for NPTL
168 sh[34]-*-linux-gnu Requires Linux 2.6.11
169 powerpc* Requires Linux 2.4.19
170 arm*-*-linux-*gnueabi Requires Linux 2.6.16
172 config LIBC_GLIBC_KERNEL_VERSION_AS_HEADERS
174 prompt "Same as kernel headers (default)"
176 Normally, you'll want glibc/eglibc to run against the same kernel
177 version as the one used for the headers.
181 If enabled, crosstool-ng will use the chosen version of kernel
182 headers for the glibc minimum kernel version supported, which is
183 what gets passed to "--enable-kernel=" when configuring glibc.
185 Enabling this will ensure that no legacy compatibility code for
186 older kernels is built into your C libraries, but it will
187 be unable to run on kernel versions older than whichever kernel
188 headers version you've built the toolchain for.
190 If you know for sure that your toolchain will never need to build
191 applications that will run under a kernel version older than your
192 chosen kernel headers version (CT_KERNEL_VERSION), you can choose
195 config LIBC_GLIBC_KERNEL_VERSION_CHOSEN
197 prompt "Specific kernel version"
199 Specify the earliest Linux kernel version you want glibc to
200 include support for. This does not have to match the kernel
201 headers version used for your toolchain. This controls what is
202 passed to the "--enable-kernel=" option to the glibc configure
205 If you want to be able to statically link programs with your
206 toolchain's C library, make sure this kernel version is lower than
207 all kernels you wish to support to avoid "FATAL: kernel too old"
208 errors. The higher the version you specify, the less legacy code
209 will be built into libc.
211 Most people can leave this at the default value of "2.6.9".
213 if LIBC_GLIBC_KERNEL_VERSION_CHOSEN
215 config LIBC_GLIBC_MIN_KERNEL_VERSION
217 prompt "Minimum kernel version to support"
220 Enter here the lowest kernel version glibc/eglibc will be able to
223 The minimum kernel version supported will be dependent upon the
224 target you build for. For example:
225 alpha*-*-linux-gnu Requires Linux 2.6.9 for NPTL
226 sh[34]-*-linux-gnu Requires Linux 2.6.11
227 powerpc* Requires Linux 2.4.19
228 arm*-*-linux-*gnueabi Requires Linux 2.6.16
230 Note that no sanity check is performed by crosstool-NG to ensure
231 that the value you enter here is appropriate for your target.
233 endif # LIBC_GLIBC_KERNEL_VERSION_CHOSEN
237 config LIBC_GLIBC_MIN_KERNEL
239 default "" if LIBC_GLIBC_KERNEL_VERSION_NONE
240 default KERNEL_VERSION if LIBC_GLIBC_KERNEL_VERSION_AS_HEADERS
241 default LIBC_GLIBC_MIN_KERNEL_VERSION if LIBC_GLIBC_KERNEL_VERSION_CHOSEN