summaryrefslogtreecommitdiffstats
path: root/toolchain/toolchain-crosstool-ng/crosstool-ng.config-uClibc
Commit message (Collapse)AuthorAgeFilesLines
* ctng: use gcc 4.4.6Peter Korsgaard2012-01-221-3/+3
| | | | Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* ctng: use 3.0.4 kernel headersPeter Korsgaard2012-01-221-3/+3
| | | | Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* ctng: use internal toolchain uClibc config, build uClibc 0.9.32Peter Korsgaard2012-01-221-3/+3
| | | | | | | So the uClibc configurations are kept in sync between the two toolchain methods. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* toolchain/ct-ng: update to 1.13.0Yann E. MORIN2011-11-021-37/+46
| | | | | | | | | 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>
* toolchain/crosstool-NG: fix bundled config filesYann E. MORIN2011-08-281-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* toolchain/crosstool-NG: update bundled config filesYann E. MORIN2011-08-071-144/+48
| | | | | | | | 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>
* toolchain/crosstool-NG: update to 1.11.3Yann E. MORIN2011-05-221-44/+78
| | | | | | | | | | | | 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>
* toolchain/crosstool-NG: bundle one CT-NG config file for each libc famillyYann E. MORIN2011-05-221-0/+436
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>
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-05 17:31:49 +0000