summaryrefslogtreecommitdiff
path: root/config
diff options
context:
space:
mode:
Diffstat (limited to 'config')
-rw-r--r--config/arch/microblaze.in2
-rw-r--r--config/binutils/binutils.in6
-rw-r--r--config/cc/gcc.in8
-rw-r--r--config/companion_libs/isl.in5
-rw-r--r--config/debug/gdb.in13
-rw-r--r--config/kernel/linux.in29
-rw-r--r--config/libc/eglibc.in.21
-rw-r--r--config/libc/glibc-eglibc.in-common268
-rw-r--r--config/libc/glibc.in.2268
-rw-r--r--config/toolchain.in2
10 files changed, 311 insertions, 291 deletions
diff --git a/config/arch/microblaze.in b/config/arch/microblaze.in
index fb38e1f..c664498 100644
--- a/config/arch/microblaze.in
+++ b/config/arch/microblaze.in
@@ -19,4 +19,4 @@
## help
## help Support is being added for a modern gcc,
## help binutils and gdb along with nptl threading
-## help in eglibc for microblaze.
+## help in glibc for microblaze.
diff --git a/config/binutils/binutils.in b/config/binutils/binutils.in
index 9800004..8c1bf87 100644
--- a/config/binutils/binutils.in
+++ b/config/binutils/binutils.in
@@ -160,8 +160,8 @@ config BINUTILS_HAS_PKGVERSION_BUGURL
bool
# Force using the BFD linker if needed
-# This is the case for some C libraries (eg. glibc and
-# eglibc at least) and affected components can select this
+# This is the case for some C libraries (eg. glibc at least) and affected
+# components can select this
config BINUTILS_FORCE_LD_BFD
bool
@@ -219,7 +219,7 @@ endchoice # Enable linkers
if BINUTILS_LINKER_GOLD
comment "WARNING! gold is not capable of"
-comment "| building glibc/eglibc!"
+comment "| building glibc!"
endif # BINUTILS_LINKER_GOLD
config BINUTILS_GOLD_INSTALLED
diff --git a/config/cc/gcc.in b/config/cc/gcc.in
index 65ecd94..a60444e 100644
--- a/config/cc/gcc.in
+++ b/config/cc/gcc.in
@@ -38,7 +38,7 @@ choice
config CC_V_linaro_4_9
bool
- prompt "linaro-4.9-2015.01"
+ prompt "linaro-4.9-2015.03"
depends on CC_GCC_SHOW_LINARO
select CC_GCC_4_9
@@ -59,7 +59,7 @@ config CC_V_4_9_0
config CC_V_linaro_4_8
bool
- prompt "linaro-4.8-2014.11"
+ prompt "linaro-4.8-2015.02"
depends on CC_GCC_SHOW_LINARO
select CC_GCC_4_8
@@ -508,11 +508,11 @@ config CC_VERSION
string
# Don't remove next line
# CT_INSERT_VERSION_STRING_BELOW
- default "linaro-4.9-2015.01" if CC_V_linaro_4_9
+ default "linaro-4.9-2015.03" if CC_V_linaro_4_9
default "4.9.2" if CC_V_4_9_2
default "4.9.1" if CC_V_4_9_1
default "4.9.0" if CC_V_4_9_0
- default "linaro-4.8-2014.11" if CC_V_linaro_4_8
+ default "linaro-4.8-2015.02" if CC_V_linaro_4_8
default "4.8.4" if CC_V_4_8_4
default "4.8.3" if CC_V_4_8_3
default "4.8.2" if CC_V_4_8_2
diff --git a/config/companion_libs/isl.in b/config/companion_libs/isl.in
index a6b53fb..92e659b 100644
--- a/config/companion_libs/isl.in
+++ b/config/companion_libs/isl.in
@@ -6,6 +6,10 @@ choice
# Don't remove next line
# CT_INSERT_VERSION_BELOW
+config ISL_V_0_14
+ bool
+ prompt "0.14"
+
config ISL_V_0_12_2
bool
prompt "0.12.2"
@@ -20,5 +24,6 @@ config ISL_VERSION
string
# Don't remove next line
# CT_INSERT_VERSION_STRING_BELOW
+ default "0.14" if ISL_V_0_14
default "0.12.2" if ISL_V_0_12_2
default "0.11.1" if ISL_V_0_11_1
diff --git a/config/debug/gdb.in b/config/debug/gdb.in
index 9ca84f5..e6366fb 100644
--- a/config/debug/gdb.in
+++ b/config/debug/gdb.in
@@ -33,12 +33,23 @@ choice
# Don't remove next line
# CT_INSERT_VERSION_BELOW
+config GDB_V_7_9
+ bool
+ prompt "7.9"
+ select GDB_7_2_or_later
+
config GDB_V_linaro_7_8
bool
prompt "linaro-7.8-2014.09"
depends on DEBUG_GDB_SHOW_LINARO
select GDB_7_2_or_later
+config GDB_V_7_8_2
+ bool
+ prompt "7.8.2"
+ select GDB_7_2_or_later
+
+
config GDB_V_7_8_1
bool
prompt "7.8.1"
@@ -174,6 +185,8 @@ config GDB_VERSION
string
# Don't remove next line
# CT_INSERT_VERSION_STRING_BELOW
+ default "7.9" if GDB_V_7_9
+ default "7.8.2" if GDB_V_7_8_2
default "linaro-7.8-2014.09" if GDB_V_linaro_7_8
default "7.8.1" if GDB_V_7_8_1
default "7.8" if GDB_V_7_8
diff --git a/config/kernel/linux.in b/config/kernel/linux.in
index f1a4c9c..20505ca 100644
--- a/config/kernel/linux.in
+++ b/config/kernel/linux.in
@@ -26,9 +26,13 @@ choice
# Don't remove next line
# CT_INSERT_VERSION_BELOW
+config KERNEL_V_3_19
+ bool
+ prompt "3.19.1"
+
config KERNEL_V_3_18
bool
- prompt "3.18.3"
+ prompt "3.18.9"
config KERNEL_V_3_17
bool
@@ -44,7 +48,7 @@ config KERNEL_V_3_15
config KERNEL_V_3_14
bool
- prompt "3.14.29 (longterm)"
+ prompt "3.14.35 (longterm)"
config KERNEL_V_3_13
bool
@@ -52,7 +56,7 @@ config KERNEL_V_3_13
config KERNEL_V_3_12
bool
- prompt "3.12.36 (longterm)"
+ prompt "3.12.38 (longterm)"
config KERNEL_V_3_11
bool
@@ -60,7 +64,7 @@ config KERNEL_V_3_11
config KERNEL_V_3_10
bool
- prompt "3.10.65 (longterm)"
+ prompt "3.10.71 (longterm)"
config KERNEL_V_3_9
bool
@@ -84,7 +88,7 @@ config KERNEL_V_3_5
config KERNEL_V_3_4
bool
- prompt "3.4.105 (longterm)"
+ prompt "3.4.106 (longterm)"
config KERNEL_V_3_3
bool
@@ -92,7 +96,7 @@ config KERNEL_V_3_3
config KERNEL_V_3_2
bool
- prompt "3.2.66 (longterm)"
+ prompt "3.2.68 (longterm)"
config KERNEL_V_3_1
bool
@@ -191,23 +195,24 @@ config KERNEL_VERSION
string
# Don't remove next line
# CT_INSERT_VERSION_STRING_BELOW
- default "3.18.3" if KERNEL_V_3_18
+ default "3.19.1" if KERNEL_V_3_19
+ default "3.18.9" if KERNEL_V_3_18
default "3.17.8" if KERNEL_V_3_17
default "3.16.7" if KERNEL_V_3_16
default "3.15.10" if KERNEL_V_3_15
- default "3.14.29" if KERNEL_V_3_14
+ default "3.14.35" if KERNEL_V_3_14
default "3.13.11" if KERNEL_V_3_13
- default "3.12.36" if KERNEL_V_3_12
+ default "3.12.38" if KERNEL_V_3_12
default "3.11.10" if KERNEL_V_3_11
- default "3.10.65" if KERNEL_V_3_10
+ default "3.10.71" if KERNEL_V_3_10
default "3.9.11" if KERNEL_V_3_9
default "3.8.13" if KERNEL_V_3_8
default "3.7.10" if KERNEL_V_3_7
default "3.6.11" if KERNEL_V_3_6
default "3.5.7" if KERNEL_V_3_5
- default "3.4.105" if KERNEL_V_3_4
+ default "3.4.106" if KERNEL_V_3_4
default "3.3.8" if KERNEL_V_3_3
- default "3.2.66" if KERNEL_V_3_2
+ default "3.2.68" if KERNEL_V_3_2
default "3.1.10" if KERNEL_V_3_1
default "3.0.101" if KERNEL_V_3_0
default "2.6.39.4" if KERNEL_V_2_6_39
diff --git a/config/libc/eglibc.in.2 b/config/libc/eglibc.in.2
deleted file mode 100644
index 84553f3..0000000
--- a/config/libc/eglibc.in.2
+++ /dev/null
@@ -1 +0,0 @@
-source "config/libc/glibc-eglibc.in-common"
diff --git a/config/libc/glibc-eglibc.in-common b/config/libc/glibc-eglibc.in-common
deleted file mode 100644
index f199e3a..0000000
--- a/config/libc/glibc-eglibc.in-common
+++ /dev/null
@@ -1,268 +0,0 @@
-# This file contains the common configuration options
-# that apply to both glibc and eglibc.
-
-# Some architectures require the ports addon. List them one by one here:
-# This list must be carefully in sync with the architectures names
-# we can find in config/arch/*
-
-config LIBC_GLIBC_PORTS_EXTERNAL
- bool
- default n
-
-config LIBC_GLIBC_MAY_FORCE_PORTS
- bool
- default y if ARCH_arm
- default y if ARCH_mips
- select LIBC_GLIBC_USE_PORTS
- depends on !LIBC_GLIBC_2_20_or_later
-
-# Force using the BFD linker during the toolchain build
-config LIBC_glibc_familly
- bool
- default y
- select BINUTILS_FORCE_LD_BFD
-
-config LIBC_GLIBC_EXTRA_CONFIG_ARRAY
- string
- prompt "extra config"
- default ""
- help
- Extra flags to pass onto ./configure when configuring.
-
- You can enter multiple arguments here, and arguments can contain spaces
- if they are properly quoted (or escaped, but prefer quotes). Eg.:
- --with-foo="1st arg with 4 spaces" --with-bar=2nd-arg-without-space
-
-config LIBC_GLIBC_CONFIGPARMS
- string
- prompt "Extra config params (READ HELP)"
- default "" if ! ARCH_sh
- default "no-z-defs=yes" if ARCH_sh
- help
- Some architectures need to set options in the file configparms.
- This is the case for sh3/4, which really need to set configparms
- to "no-z-defs=yes" as of gcc-3.4/glibc-2.3.2.
-
- Unless you are building a toolchain for sh3/4, you should leave that empty.
-
- Note: If you need to pass more than one value, separate them with
- '\n'. Eg.: var1=val1\nvar2=val2
-
-config LIBC_GLIBC_EXTRA_CFLAGS
- string
- prompt "extra target CFLAGS"
- default ""
- help
- Extra target CFLAGS to use when building.
-
-config LIBC_EXTRA_CC_ARGS
- string
- prompt "gcc extra flags"
- default ""
- help
- Extra flags to pass gcc when building.
-
- Seldom used, except for sparc64 which seems to need the flag -64
- to be passed onto gcc.
-
-config LIBC_ENABLE_FORTIFIED_BUILD
- bool
- prompt "Enable fortified build (EXPERIMENTAL)"
- depends on EXPERIMENTAL
- help
- If you say 'y' here, then glibc will be using fortified versions
- of functions with format arguments (eg. vsyslog, printf...), and
- do a sanity check on the format at runtime, to avoid some of the
- common format string attacks.
-
- This is currently not supported, and will most probably result in
- a broken build, with an error message like:
- ../misc/syslog.c: In function '__vsyslog_chk':
- ../misc/syslog.c:123: sorry, unimplemented: inlining failed in
- call to 'syslog': function body not available
-
- If you are brave enough and want to debug the issue, then say 'y'
- here. Otherwise, be still and say 'n' (the default). ;-)
-
-
-config LIBC_DISABLE_VERSIONING
- bool
- prompt "Disable symbols versioning"
- help
- Do not include versioning information in the library objects.
-
-config LIBC_OLDEST_ABI
- string
- prompt "Oldest supported ABI"
- default ""
- help
- Set the oldest ABI supported by the C library.
-
- Setting this option, for example, to 2.2 will provide ABI support
- back to (e)glibc-2.2.
-
- If this option is not set, (e)glibc will choose for you.
-
-config LIBC_GLIBC_FORCE_UNWIND
- bool
- prompt "Force unwind support (READ HELP!)"
- default y
- help
- If your toolchain fails building while building the C library
- start files, or the complete C library, with a message like:
- configure: error: forced unwind support is required
-
- then you may try changing this option. Otherwise, leave it to
- the default 'y'.
-
- The issue seems to be related to building NPTL on old versions
- of glibc (and possibly eglibc as well) on some architectures
- (seen on s390, s390x and x86_64).
-
-config LIBC_GLIBC_USE_PORTS
- bool
- prompt "Use the ports addon"
- depends on !LIBC_GLIBC_2_20_or_later
- help
- The ports addon contains some architecture ports that are not available
- in the official distribution.
-
- For example, this is the case for ARM with glibc-2.4 and above.
-
- Say n only if you're sure that your architecture is in the official
- distribution for your chosen version.
-
-config LIBC_ADDONS_LIST
- string
- prompt "Extra addons"
- default ""
- help
- Extra addons to include. Space separated list.
-
- You need to specify neither linuxthreads nor nptl, as they are added
- automagically for you depending on the threading model you chose
- earlier.
-
- Eg.: crypt (for very old libces)
-
-if LIBC_GLIBC_USE_PORTS || ( LIBC_ADDONS_LIST != "" )
-comment "WARNING !!! "
-comment "| For glibc >= 2.8, it can happen that the tarballs "
-comment "| for the addons are not available for download. "
-comment "| If that happens, bad luck... Try a previous version "
-comment "| or try again later... :-( "
-endif
-
-config LIBC_LOCALES
- bool
- prompt "Build and install locales"
- help
- Whether to build and install the libc locale files for the target,
- which is required in order to support internationalization.
-
-if LIBC_glibc && LIBC_LOCALES
-comment "WARNING! "
-comment "| The built locales will be usable if and only if the build "
-comment "| machine and the target: "
-comment "| - have the same endianness, "
-comment "| - and have the same alignment requirements for uint32_t. "
-comment "| You will have to check by yourself (for now). "
-endif # LIBC_glibc && LIBC_LOCALES
-
-if KERNEL_linux
-
-choice LIBC_GLIBC_SUPPORTED_KERNEL
- bool
- prompt "Minimum supported kernel version"
- default LIBC_GLIBC_KERNEL_VERSION_AS_HEADERS
-
-config LIBC_GLIBC_KERNEL_VERSION_NONE
- bool
- prompt "Let ./configure decide"
- help
- Let ./configure decide what minimum kernel version glibc/eglibc
- will be able to run against.
-
- This will include legacy compatibility code for older kernels in
- the C library, thus ensuring that it will run on a large number
- of old kernels.
-
- The minimum kernel version supported will be dependent upon the
- target you build for. For example:
- alpha*-*-linux-gnu Requires Linux 2.6.9 for NPTL
- sh[34]-*-linux-gnu Requires Linux 2.6.11
- powerpc* Requires Linux 2.4.19
- arm*-*-linux-*gnueabi Requires Linux 2.6.16
-
-config LIBC_GLIBC_KERNEL_VERSION_AS_HEADERS
- bool
- prompt "Same as kernel headers (default)"
- help
- Normally, you'll want glibc/eglibc to run against the same kernel
- version as the one used for the headers.
-
- This is the default.
-
- If enabled, crosstool-ng will use the chosen version of kernel
- headers for the glibc minimum kernel version supported, which is
- what gets passed to "--enable-kernel=" when configuring glibc.
-
- Enabling this will ensure that no legacy compatibility code for
- older kernels is built into your C libraries, but it will
- be unable to run on kernel versions older than whichever kernel
- headers version you've built the toolchain for.
-
- If you know for sure that your toolchain will never need to build
- applications that will run under a kernel version older than your
- chosen kernel headers version (CT_KERNEL_VERSION), you can choose
- "y" here.
-
-config LIBC_GLIBC_KERNEL_VERSION_CHOSEN
- bool
- prompt "Specific kernel version"
- help
- Specify the earliest Linux kernel version you want glibc to
- include support for. This does not have to match the kernel
- headers version used for your toolchain. This controls what is
- passed to the "--enable-kernel=" option to the glibc configure
- script.
-
- If you want to be able to statically link programs with your
- toolchain's C library, make sure this kernel version is lower than
- all kernels you wish to support to avoid "FATAL: kernel too old"
- errors. The higher the version you specify, the less legacy code
- will be built into libc.
-
- Most people can leave this at the default value of "2.6.9".
-
-if LIBC_GLIBC_KERNEL_VERSION_CHOSEN
-
-config LIBC_GLIBC_MIN_KERNEL_VERSION
- string
- prompt "Minimum kernel version to support"
- default "2.6.9"
- help
- Enter here the lowest kernel version glibc/eglibc will be able to
- run against.
-
- The minimum kernel version supported will be dependent upon the
- target you build for. For example:
- alpha*-*-linux-gnu Requires Linux 2.6.9 for NPTL
- sh[34]-*-linux-gnu Requires Linux 2.6.11
- powerpc* Requires Linux 2.4.19
- arm*-*-linux-*gnueabi Requires Linux 2.6.16
-
- Note that no sanity check is performed by crosstool-NG to ensure
- that the value you enter here is appropriate for your target.
-
-endif # LIBC_GLIBC_KERNEL_VERSION_CHOSEN
-
-endchoice
-
-config LIBC_GLIBC_MIN_KERNEL
- string
- default "" if LIBC_GLIBC_KERNEL_VERSION_NONE
- default KERNEL_VERSION if LIBC_GLIBC_KERNEL_VERSION_AS_HEADERS
- default LIBC_GLIBC_MIN_KERNEL_VERSION if LIBC_GLIBC_KERNEL_VERSION_CHOSEN
-
-endif # KERNEL_linux
diff --git a/config/libc/glibc.in.2 b/config/libc/glibc.in.2
index 84553f3..346f9b7 100644
--- a/config/libc/glibc.in.2
+++ b/config/libc/glibc.in.2
@@ -1 +1,267 @@
-source "config/libc/glibc-eglibc.in-common"
+# This file contains the common configuration options
+# that apply to both glibc.
+
+# Some architectures require the ports addon. List them one by one here:
+# This list must be carefully in sync with the architectures names
+# we can find in config/arch/*
+
+config LIBC_GLIBC_PORTS_EXTERNAL
+ bool
+ default n
+
+config LIBC_GLIBC_MAY_FORCE_PORTS
+ bool
+ default y if ARCH_arm
+ default y if ARCH_mips
+ select LIBC_GLIBC_USE_PORTS
+ depends on !LIBC_GLIBC_2_20_or_later
+
+# Force using the BFD linker during the toolchain build
+config LIBC_glibc_familly
+ bool
+ default y
+ select BINUTILS_FORCE_LD_BFD
+
+config LIBC_GLIBC_EXTRA_CONFIG_ARRAY
+ string
+ prompt "extra config"
+ default ""
+ help
+ Extra flags to pass onto ./configure when configuring.
+
+ You can enter multiple arguments here, and arguments can contain spaces
+ if they are properly quoted (or escaped, but prefer quotes). Eg.:
+ --with-foo="1st arg with 4 spaces" --with-bar=2nd-arg-without-space
+
+config LIBC_GLIBC_CONFIGPARMS
+ string
+ prompt "Extra config params (READ HELP)"
+ default "" if ! ARCH_sh
+ default "no-z-defs=yes" if ARCH_sh
+ help
+ Some architectures need to set options in the file configparms.
+ This is the case for sh3/4, which really need to set configparms
+ to "no-z-defs=yes" as of gcc-3.4/glibc-2.3.2.
+
+ Unless you are building a toolchain for sh3/4, you should leave that empty.
+
+ Note: If you need to pass more than one value, separate them with
+ '\n'. Eg.: var1=val1\nvar2=val2
+
+config LIBC_GLIBC_EXTRA_CFLAGS
+ string
+ prompt "extra target CFLAGS"
+ default ""
+ help
+ Extra target CFLAGS to use when building.
+
+config LIBC_EXTRA_CC_ARGS
+ string
+ prompt "gcc extra flags"
+ default ""
+ help
+ Extra flags to pass gcc when building.
+
+ Seldom used, except for sparc64 which seems to need the flag -64
+ to be passed onto gcc.
+
+config LIBC_ENABLE_FORTIFIED_BUILD
+ bool
+ prompt "Enable fortified build (EXPERIMENTAL)"
+ depends on EXPERIMENTAL
+ help
+ If you say 'y' here, then glibc will be using fortified versions
+ of functions with format arguments (eg. vsyslog, printf...), and
+ do a sanity check on the format at runtime, to avoid some of the
+ common format string attacks.
+
+ This is currently not supported, and will most probably result in
+ a broken build, with an error message like:
+ ../misc/syslog.c: In function '__vsyslog_chk':
+ ../misc/syslog.c:123: sorry, unimplemented: inlining failed in
+ call to 'syslog': function body not available
+
+ If you are brave enough and want to debug the issue, then say 'y'
+ here. Otherwise, be still and say 'n' (the default). ;-)
+
+
+config LIBC_DISABLE_VERSIONING
+ bool
+ prompt "Disable symbols versioning"
+ help
+ Do not include versioning information in the library objects.
+
+config LIBC_OLDEST_ABI
+ string
+ prompt "Oldest supported ABI"
+ default ""
+ help
+ Set the oldest ABI supported by the C library.
+
+ Setting this option, for example, to 2.2 will provide ABI support
+ back to (e)glibc-2.2.
+
+ If this option is not set, (e)glibc will choose for you.
+
+config LIBC_GLIBC_FORCE_UNWIND
+ bool
+ prompt "Force unwind support (READ HELP!)"
+ default y
+ help
+ If your toolchain fails building while building the C library
+ start files, or the complete C library, with a message like:
+ configure: error: forced unwind support is required
+
+ then you may try changing this option. Otherwise, leave it to
+ the default 'y'.
+
+ The issue seems to be related to building NPTL on old versions
+ of glibc on some architectures
+ (seen on s390, s390x and x86_64).
+
+config LIBC_GLIBC_USE_PORTS
+ bool
+ prompt "Use the ports addon"
+ depends on !LIBC_GLIBC_2_20_or_later
+ help
+ The ports addon contains some architecture ports that are not available
+ in the official distribution.
+
+ For example, this is the case for ARM with glibc-2.4 and above.
+
+ Say n only if you're sure that your architecture is in the official
+ distribution for your chosen version.
+
+config LIBC_ADDONS_LIST
+ string
+ prompt "Extra addons"
+ default ""
+ help
+ Extra addons to include. Space separated list.
+
+ You need to specify neither linuxthreads nor nptl, as they are added
+ automagically for you depending on the threading model you chose
+ earlier.
+
+ Eg.: crypt (for very old libces)
+
+if LIBC_GLIBC_USE_PORTS || ( LIBC_ADDONS_LIST != "" )
+comment "WARNING !!! "
+comment "| For glibc >= 2.8, it can happen that the tarballs "
+comment "| for the addons are not available for download. "
+comment "| If that happens, bad luck... Try a previous version "
+comment "| or try again later... :-( "
+endif
+
+config LIBC_LOCALES
+ bool
+ prompt "Build and install locales"
+ help
+ Whether to build and install the libc locale files for the target,
+ which is required in order to support internationalization.
+
+if LIBC_glibc && LIBC_LOCALES
+comment "WARNING! "
+comment "| The built locales will be usable if and only if the build "
+comment "| machine and the target: "
+comment "| - have the same endianness, "
+comment "| - and have the same alignment requirements for uint32_t. "
+comment "| You will have to check by yourself (for now). "
+endif # LIBC_glibc && LIBC_LOCALES
+
+if KERNEL_linux
+
+choice LIBC_GLIBC_SUPPORTED_KERNEL
+ bool
+ prompt "Minimum supported kernel version"
+ default LIBC_GLIBC_KERNEL_VERSION_AS_HEADERS
+
+config LIBC_GLIBC_KERNEL_VERSION_NONE
+ bool
+ prompt "Let ./configure decide"
+ help
+ Let ./configure decide what minimum kernel version glibc will be
+ able to run against.
+
+ This will include legacy compatibility code for older kernels in
+ the C library, thus ensuring that it will run on a large number
+ of old kernels.
+
+ The minimum kernel version supported will be dependent upon the
+ target you build for. For example:
+ alpha*-*-linux-gnu Requires Linux 2.6.9 for NPTL
+ sh[34]-*-linux-gnu Requires Linux 2.6.11
+ powerpc* Requires Linux 2.4.19
+ arm*-*-linux-*gnueabi Requires Linux 2.6.16
+
+config LIBC_GLIBC_KERNEL_VERSION_AS_HEADERS
+ bool
+ prompt "Same as kernel headers (default)"
+ help
+ Normally, you'll want glibc to run against the same kernel
+ version as the one used for the headers.
+
+ This is the default.
+
+ If enabled, crosstool-ng will use the chosen version of kernel
+ headers for the glibc minimum kernel version supported, which is
+ what gets passed to "--enable-kernel=" when configuring glibc.
+
+ Enabling this will ensure that no legacy compatibility code for
+ older kernels is built into your C libraries, but it will
+ be unable to run on kernel versions older than whichever kernel
+ headers version you've built the toolchain for.
+
+ If you know for sure that your toolchain will never need to build
+ applications that will run under a kernel version older than your
+ chosen kernel headers version (CT_KERNEL_VERSION), you can choose
+ "y" here.
+
+config LIBC_GLIBC_KERNEL_VERSION_CHOSEN
+ bool
+ prompt "Specific kernel version"
+ help
+ Specify the earliest Linux kernel version you want glibc to
+ include support for. This does not have to match the kernel
+ headers version used for your toolchain. This controls what is
+ passed to the "--enable-kernel=" option to the glibc configure
+ script.
+
+ If you want to be able to statically link programs with your
+ toolchain's C library, make sure this kernel version is lower than
+ all kernels you wish to support to avoid "FATAL: kernel too old"
+ errors. The higher the version you specify, the less legacy code
+ will be built into libc.
+
+ Most people can leave this at the default value of "2.6.9".
+
+if LIBC_GLIBC_KERNEL_VERSION_CHOSEN
+
+config LIBC_GLIBC_MIN_KERNEL_VERSION
+ string
+ prompt "Minimum kernel version to support"
+ default "2.6.9"
+ help
+ Enter here the lowest kernel version glibc will be able to run against.
+
+ The minimum kernel version supported will be dependent upon the
+ target you build for. For example:
+ alpha*-*-linux-gnu Requires Linux 2.6.9 for NPTL
+ sh[34]-*-linux-gnu Requires Linux 2.6.11
+ powerpc* Requires Linux 2.4.19
+ arm*-*-linux-*gnueabi Requires Linux 2.6.16
+
+ Note that no sanity check is performed by crosstool-NG to ensure
+ that the value you enter here is appropriate for your target.
+
+endif # LIBC_GLIBC_KERNEL_VERSION_CHOSEN
+
+endchoice
+
+config LIBC_GLIBC_MIN_KERNEL
+ string
+ default "" if LIBC_GLIBC_KERNEL_VERSION_NONE
+ default KERNEL_VERSION if LIBC_GLIBC_KERNEL_VERSION_AS_HEADERS
+ default LIBC_GLIBC_MIN_KERNEL_VERSION if LIBC_GLIBC_KERNEL_VERSION_CHOSEN
+
+endif # KERNEL_linux
diff --git a/config/toolchain.in b/config/toolchain.in
index b242444..5048e91 100644
--- a/config/toolchain.in
+++ b/config/toolchain.in
@@ -77,7 +77,7 @@ config TOOLCHAIN_PKGVERSION
help
Specify a string that identifies your package. You may wish to include
a build number or build date. This version string will be included in
- the output of gcc --version, and also in binutils, eglibc, gdb and
+ the output of gcc --version, and also in binutils, glibc, gdb and
gdbserver.
If this string is left empty, the actual package version will be: