yann@808: # This file contains the common configuration options yann@808: # that apply to both glibc and eglibc. yann@808: # yann@808: # Please note: yann@808: # the symlink is a hack around the fact that mconf can not parse yann@808: # the same file more than once, and errors out if it is the case. yann@808: # If mconf is updated to accept multiple inclusion of the same yann@808: # file, then the symlink can go (and the includers be updated). yann@808: yann@808: config LIBC_GLIBC_EXTRA_CONFIG yann@808: string yann@808: prompt "extra config" yann@808: default "" yann@808: help yann@808: Extra flags to pass onto ./configure when configuring. yann@808: yann@808: Eg.: --enable-static-nss yann@808: yann@808: config LIBC_GLIBC_EXTRA_CFLAGS yann@808: string yann@808: prompt "extra target CFLAGS" yann@808: default "" yann@808: help yann@808: Extra target CFLAGS to use when building. yann@808: yann@808: config LIBC_EXTRA_CC_ARGS yann@808: string yann@808: prompt "gcc extra flags" yann@808: default "" yann@808: help yann@808: Extra flags to pass gcc when building. yann@808: yann@808: Seldom used, except for sparc64 which seems to need the flag -64 yann@808: to be passed onto gcc. yann@808: yann@808: config LIBC_GLIBC_USE_PORTS yann@808: bool yann@808: prompt "Use the ports addon" yann@808: default n yann@808: help yann@808: The ports addon contains some architecture ports that are not available yann@808: in the official distribution. yann@808: yann@808: For example, this is the case for ARM with for 2.4 and above. yann@808: yann@808: Say n only if you're sure that your architecture is in the official yann@808: distribution for your chosen version. yann@808: yann@808: config LIBC_ADDONS yann@808: bool yann@808: prompt "Pass extra addons list" yann@808: default n yann@808: help yann@808: If you say Y here, you'll be able to give the list of addons you want to yann@808: include in your C library. yann@808: yann@808: config LIBC_ADDONS_LIST yann@808: string yann@808: prompt "Extra addons" yann@808: default "" yann@808: depends on LIBC_ADDONS yann@808: help yann@808: Extra addons to include. Space separated list. yann@808: yann@808: You need to specify neither linuxthreads nor nptl, as they are added yann@808: automagically for you depending on the threading model you choosed yann@808: earlier. yann@808: yann@808: Eg.: crypt (for very old libces) yann@810: yann@810: config LIBC_GLIBC_USE_HEADERS_MIN_KERNEL yann@810: bool yann@810: prompt "Use headers version for minimum kernel version supported" yann@810: default y yann@810: help yann@810: If enabled, crosstool-ng will use the chosen version of kernel yann@810: headers for the glibc minimum kernel version supported, which is yann@810: what gets passed to "--enable-kernel=" when configuring glibc. yann@810: yann@810: Enabling this will ensure that no legacy compatibility code for yann@810: older kernels is built into your C libraries, but it will yann@810: be unable to run on kernel versions older than whichever kernel yann@810: headers version you've built the toolchain for. yann@810: yann@810: If you know for sure that your toolchain will never need to build yann@810: applications that will run under a kernel version older than your yann@810: chosen kernel headers version (CT_KERNEL_VERSION), you can choose yann@810: "y" here. yann@810: yann@810: config LIBC_GLIBC_MIN_KERNEL_CHOSEN yann@810: string yann@810: prompt "Minimum kernel version supported" yann@810: default "2.6.9" yann@810: depends on ! LIBC_GLIBC_USE_HEADERS_MIN_KERNEL yann@810: help yann@810: Specify the earliest Linux kernel version you want glibc to yann@810: include support for. This does not have to match the kernel yann@810: headers version used for your toolchain. This controls what is yann@810: passed to the "--enable-kernel=" option to the glibc configure yann@810: script. yann@810: yann@810: If you want to be able to statically link programs with your yann@810: toolchain's C library, make sure this kernel version is lower than yann@810: all kernels you wish to support to avoid "FATAL: kernel too old" yann@810: errors. The higher the version you specify, the less legacy code yann@810: will be built into libc. yann@810: yann@810: Most people can leave this at the default value of "2.6.9". yann@810: yann@810: config LIBC_GLIBC_MIN_KERNEL yann@810: string yann@810: default KERNEL_VERSION if LIBC_GLIBC_USE_HEADERS_MIN_KERNEL yann@810: default LIBC_GLIBC_MIN_KERNEL_CHOSEN if ! LIBC_GLIBC_USE_HEADERS_MIN_KERNEL