buildroot.git/toolchain/toolchain-crosstool-ng, branch 2011.11

toolchain/ct-ng: update to 1.13.0

2011-11-02T08:32:41Z

Update the version in the package description. Update the default configuration files for the three different C libraries. [Peter: Removed unneeded changes as noticed by Baruch Siach] Signed-off-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard

toolchain/crosstool-NG: fix bundled config files

2011-08-28T07:43:21Z

Bundled config files have architecture-specific values in them, which may break if buildroot is configured with another architecture that does not forcibly set these option. For example, the bundled config files are for x86_64, and define: CT_ARCH_TUNE="generic" This comes from the BR2_GCC_TARGET_TUNE config option (in buildroot) that is set accordingly to the selected (arch,sub-arch). But if someone configures buildroot for, say, generic ARM, then the BR2_GCC_TARGET_TUNE config option is not set, and the crosstool-NG backend Makefile believes it should not be pushed down to the crosstool-NG config file. BUT... The crosstool-NG backend Makefile can not forcibly push BR2_GCC_TARGET_TUNE down to the CT-NG config file. If BR2_GCC_TARGET_TUNE is empty, the user can still set CT_ARCH_TUNE by running ctng-menuconfig. The backend Makefile already passes such values only if they are set. In the end, we can't push options as-is to the crosstool-NG config, but we MUST provide sane bundled config files, which this patch does. Signed-off-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard

toolchain/crosstool-NG: update bundled config files

2011-08-07T21:17:49Z

Update the crosstool-NG libc-specific config files to match the new set of options coming with the updated crosstool-NG. Signed-off-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard

toochain/crosstool-NG: bump version

2011-08-07T21:17:03Z

Signed-off-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard

uClibc: drop BR2_PROGRAM_INVOCATION option

2011-07-27T09:56:53Z

Remove the BR option and enable the configuration setting in the uClibc defconfigs. The BR2_PROGRAM_INVOCATION option only adds very little overhead to uClibc, and we have a number of packages needing it, so simply always enable it - Simplifying the kconfig logic and the number of choices users have to make. Signed-off-by: Peter Korsgaard

toolchain/crosstool-NG: use the package infrastructure

2011-07-15T20:58:38Z

Move crosstool-NG to package/ and make it an autotarget package. This requires a new patch (now upstream). Now, the crosstool-NG toolchain backend only contains enough to build the toolchain, there's no more reference to building crosstool-NG as a package. Signed-off-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard

toolchain/crosstool-ng: allow pre-downloading the sources

2011-07-13T06:31:05Z

On "make source", just download the required sources, and do not build the entire toolchain. This requires a new patch against crosstool-NG (got from upstream). The "uclibc-source" rule requires an installed and configured crosstool-NG, so it has to be after the variables declaration. For consistency, move down the main rule "uclibc". Signed-off-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard

toolchain/crosstool-NG: fix up ct-ng config file to saner defaults

2011-05-22T08:19:13Z

Peter on IRC reported some build failures for different targets. They were of two kinds: - missing/unknown stack unwinding support - missing *_chk functions The first is about configure not being able to automagically determine if stack unwinding support is available for the target. The second is about fortified build forgetting to build the fortified functions. This applies to both glibc and eglibc. After some discussions on IRC with Jacmet, it appears that we can safely assume both of the following: - virtually all targets of buildroot will have stack unwinding support - we do not care about fortified builds (so far) So, update the bundled crosstool-NG .config file to saner defaults: - force unwind support - disable fortified builds [Peter: fix 'force non-fortified build' sed invocation] Reported-by: Peter Korsgaard Signed-off-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard

toolchain/crosstool-NG: update to 1.11.3

2011-05-22T08:04:29Z

1.11.3 is the latest stable version, and it has a few improvements we'll find usefull. For example, it hasa a boolean option for disabling the {,e}glibc fortified build (instead of requiring us to shoehorn it in extra cflags. Update the config files. Signed-off-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard

toolchain/crosstool-NG: bundle one CT-NG config file for each libc familly

2011-05-22T08:04:27Z

Currently, the bundled CT-NG config file has no C library configured. It is quite complex to add and/or munge options in this case. Now, with one config file per libc familly, it becomes easier. Signed-off-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard