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 Eg.: --enable-static-nss
28 config LIBC_GLIBC_CONFIGPARMS
30 prompt "Extra config params (READ HELP)"
31 default "" if ! ARCH_sh
32 default "no-z-defs=yes" if ARCH_sh
34 Some architectures need to set options in the file configparms.
35 This is the case for sh3/4, which really need to set configparms
36 to "no-z-defs=yes" as of gcc-3.4/glibc-2.3.2.
38 Unless you are building a toolchain for sh3/4, you should leave that empty.
40 Note: If you need to pass more than one value, separate them with
41 '\n'. Eg.: var1=val1\nvar2=val2
43 config LIBC_GLIBC_EXTRA_CFLAGS
45 prompt "extra target CFLAGS"
48 Extra target CFLAGS to use when building.
50 config LIBC_EXTRA_CC_ARGS
52 prompt "gcc extra flags"
55 Extra flags to pass gcc when building.
57 Seldom used, except for sparc64 which seems to need the flag -64
58 to be passed onto gcc.
60 config LIBC_ENABLE_FORTIFIED_BUILD
62 prompt "Enable fortified build (EXPERIMENTAL)"
63 depends on EXPERIMENTAL
66 If you say 'y' here, then glibc will be using fortified versions
67 of functions with format arguments (eg. vsyslog, printf...), and
68 do a sanity check on the format at runtime, to avoid some of the
69 common format string attacks.
71 This is currently not supported, and will most probably result in
72 a broken build, with an error message like:
73 ../misc/syslog.c: In function '__vsyslog_chk':
74 ../misc/syslog.c:123: sorry, unimplemented: inlining failed in
75 call to 'syslog': function body not available
77 If you are brave enough and want to debug the issue, then say 'y'
78 here. Otherwise, be still and say 'n' (the default). ;-)
81 config LIBC_DISABLE_VERSIONING
83 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!)"
105 If your toolchain fails building while building the C library
106 start files, or the complete C library, with a message like:
107 configure: error: forced unwind support is required
109 then you may try setting this to 'y'. Otherwise, leave it to 'n'.
111 The issue seems to be related to building NPTL on old versions
112 of glibc (and possibly eglibc as well) on some architectures
113 (seen on s390, s390x and x86_64).
115 config LIBC_GLIBC_USE_PORTS
117 prompt "Use the ports addon"
120 The ports addon contains some architecture ports that are not available
121 in the official distribution.
123 For example, this is the case for ARM with glibc-2.4 and above.
125 Say n only if you're sure that your architecture is in the official
126 distribution for your chosen version.
128 config LIBC_ADDONS_LIST
130 prompt "Extra addons"
133 Extra addons to include. Space separated list.
135 You need to specify neither linuxthreads nor nptl, as they are added
136 automagically for you depending on the threading model you choosed
139 Eg.: crypt (for very old libces)
141 if LIBC_GLIBC_USE_PORTS || ( LIBC_ADDONS_LIST != "" )
142 comment "WARNING !!! "
143 comment "| For glibc >= 2.8, it can happen that the tarballs "
144 comment "| for the addons are not available for download. "
145 comment "| If that happens, bad luck... Try a previous version "
146 comment "| or try again later... :-( "
151 choice LIBC_GLIBC_SUPPORTED_KERNEL
153 prompt "Minimum supported kernel version"
154 default LIBC_GLIBC_KERNEL_VERSION_AS_HEADERS
156 config LIBC_GLIBC_KERNEL_VERSION_NONE
158 prompt "Let ./configure decide"
160 Let ./configure decide what minimum kernel version glibc/eglibc
161 will be able to run against.
163 This will inclde legacy compatibility code for older kernels in
164 the C library, thus ensuring that it will run on a large number
167 The minimum kernel version supported will be dependent upon the
168 target you build for. For example:
169 alpha*-*-linux-gnu Requires Linux 2.6.9 for NPTL
170 sh[34]-*-linux-gnu Requires Linux 2.6.11
171 powerpc* Requires Linux 2.4.19
172 arm*-*-linux-*gnueabi Requires Linux 2.6.16
174 config LIBC_GLIBC_KERNEL_VERSION_AS_HEADERS
176 prompt "Same as kernel headers (default)"
178 Normaly, you'll want glibc/eglibc to run against the same kernel
179 version as the one used for the headers.
183 If enabled, crosstool-ng will use the chosen version of kernel
184 headers for the glibc minimum kernel version supported, which is
185 what gets passed to "--enable-kernel=" when configuring glibc.
187 Enabling this will ensure that no legacy compatibility code for
188 older kernels is built into your C libraries, but it will
189 be unable to run on kernel versions older than whichever kernel
190 headers version you've built the toolchain for.
192 If you know for sure that your toolchain will never need to build
193 applications that will run under a kernel version older than your
194 chosen kernel headers version (CT_KERNEL_VERSION), you can choose
197 config LIBC_GLIBC_KERNEL_VERSION_CHOSEN
199 prompt "Specific kernel version"
201 Specify the earliest Linux kernel version you want glibc to
202 include support for. This does not have to match the kernel
203 headers version used for your toolchain. This controls what is
204 passed to the "--enable-kernel=" option to the glibc configure
207 If you want to be able to statically link programs with your
208 toolchain's C library, make sure this kernel version is lower than
209 all kernels you wish to support to avoid "FATAL: kernel too old"
210 errors. The higher the version you specify, the less legacy code
211 will be built into libc.
213 Most people can leave this at the default value of "2.6.9".
215 if LIBC_GLIBC_KERNEL_VERSION_CHOSEN
217 config LIBC_GLIBC_MIN_KERNEL_VERSION
219 prompt "Minimum kernel version to support"
222 Enter here the lowest kernel version glibc/eglibc will be able to
225 The minimum kernel version supported will be dependent upon the
226 target you build for. For example:
227 alpha*-*-linux-gnu Requires Linux 2.6.9 for NPTL
228 sh[34]-*-linux-gnu Requires Linux 2.6.11
229 powerpc* Requires Linux 2.4.19
230 arm*-*-linux-*gnueabi Requires Linux 2.6.16
232 Note that no sanity check is performed by crosstool-NG to ensure
233 that the value you enter here is appropriate for your target.
235 endif # LIBC_GLIBC_KERNEL_VERSION_CHOSEN
239 config LIBC_GLIBC_MIN_KERNEL
241 default "" if LIBC_GLIBC_KERNEL_VERSION_NONE
242 default KERNEL_VERSION if LIBC_GLIBC_KERNEL_VERSION_AS_HEADERS
243 default LIBC_GLIBC_MIN_KERNEL_VERSION if LIBC_GLIBC_KERNEL_VERSION_CHOSEN