Fix auto-completion for updaetools.
/trunk/ct-ng.comp | 2 1 1 0 +-
1 file changed, 1 insertion(+), 1 deletion(-)
1 # This file contains the common configuration options
2 # that apply to both glibc and eglibc.
5 # the symlink is a hack around the fact that mconf can not parse
6 # the same file more than once, and errors out if it is the case.
7 # If mconf is updated to accept multiple inclusion of the same
8 # file, then the symlink can go (and the includers be updated).
10 config LIBC_GLIBC_EXTRA_CONFIG
15 Extra flags to pass onto ./configure when configuring.
17 Eg.: --enable-static-nss
19 config LIBC_GLIBC_EXTRA_CFLAGS
21 prompt "extra target CFLAGS"
24 Extra target CFLAGS to use when building.
26 config LIBC_EXTRA_CC_ARGS
28 prompt "gcc extra flags"
31 Extra flags to pass gcc when building.
33 Seldom used, except for sparc64 which seems to need the flag -64
34 to be passed onto gcc.
36 config LIBC_GLIBC_USE_PORTS
38 prompt "Use the ports addon"
41 The ports addon contains some architecture ports that are not available
42 in the official distribution.
44 For example, this is the case for ARM with for 2.4 and above.
46 Say n only if you're sure that your architecture is in the official
47 distribution for your chosen version.
51 prompt "Pass extra addons list"
54 If you say Y here, you'll be able to give the list of addons you want to
55 include in your C library.
57 config LIBC_ADDONS_LIST
61 depends on LIBC_ADDONS
63 Extra addons to include. Space separated list.
65 You need to specify neither linuxthreads nor nptl, as they are added
66 automagically for you depending on the threading model you choosed
69 Eg.: crypt (for very old libces)
71 config LIBC_GLIBC_USE_HEADERS_MIN_KERNEL
73 prompt "Use headers version for minimum kernel version supported"
76 If enabled, crosstool-ng will use the chosen version of kernel
77 headers for the glibc minimum kernel version supported, which is
78 what gets passed to "--enable-kernel=" when configuring glibc.
80 Enabling this will ensure that no legacy compatibility code for
81 older kernels is built into your C libraries, but it will
82 be unable to run on kernel versions older than whichever kernel
83 headers version you've built the toolchain for.
85 If you know for sure that your toolchain will never need to build
86 applications that will run under a kernel version older than your
87 chosen kernel headers version (CT_KERNEL_VERSION), you can choose
90 config LIBC_GLIBC_MIN_KERNEL_CHOSEN
92 prompt "Minimum kernel version supported"
94 depends on ! LIBC_GLIBC_USE_HEADERS_MIN_KERNEL
96 Specify the earliest Linux kernel version you want glibc to
97 include support for. This does not have to match the kernel
98 headers version used for your toolchain. This controls what is
99 passed to the "--enable-kernel=" option to the glibc configure
102 If you want to be able to statically link programs with your
103 toolchain's C library, make sure this kernel version is lower than
104 all kernels you wish to support to avoid "FATAL: kernel too old"
105 errors. The higher the version you specify, the less legacy code
106 will be built into libc.
108 Most people can leave this at the default value of "2.6.9".
110 config LIBC_GLIBC_MIN_KERNEL
112 default KERNEL_VERSION if LIBC_GLIBC_USE_HEADERS_MIN_KERNEL
113 default LIBC_GLIBC_MIN_KERNEL_CHOSEN if ! LIBC_GLIBC_USE_HEADERS_MIN_KERNEL