Commit Graph

7 Commits

Author SHA1 Message Date
Peter Korsgaard
5c8747d2c4 ctng: use gcc 4.4.6
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-01-22 22:54:58 +01:00
Peter Korsgaard
5fd3015c7e ctng: use 3.0.4 kernel headers
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-01-22 22:53:19 +01:00
Yann E. MORIN
c872a748b0 toolchain/ct-ng: update to 1.13.0
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" <yann.morin.1998@anciens.enib.fr>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-11-02 09:32:41 +01:00
Yann E. MORIN
f30928c1b1 toolchain/crosstool-NG: fix bundled config files
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" <yann.morin.1998@anciens.enib.fr>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-08-28 09:43:21 +02:00
Yann E. MORIN
c72a9bd4c8 toolchain/crosstool-NG: update bundled config files
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" <yann.morin.1998@anciens.enib.fr>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-08-07 23:17:49 +02:00
Yann E. MORIN
4943afcc91 toolchain/crosstool-NG: update to 1.11.3
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" <yann.morin.1998@anciens.enib.fr>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-05-22 10:04:29 +02:00
Yann E. MORIN
f5268b171a toolchain/crosstool-NG: bundle one CT-NG config file for each libc familly
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" <yann.morin.1998@anciens.enib.fr>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-05-22 10:04:27 +02:00