path: root/config
AgeCommit message (Collapse)AuthorFilesLines
2011-05-08cc/gcc: fix complibs dependencyYann E. MORIN"1-1/+1
Since the gcc configuration changes, the way to select the dependent companion libraries has changed. The addToolVersion script was not updated to match, and a new gcc version was added with this script. Fix the gcc version; the script will be updated in a subsequent changeset. Reported-by: Xun Li <> Signed-off-by: "Yann E. MORIN" <> (transplanted from 79947df7ec4b482297ba90c3fe77314336d200e5)
2011-04-28debug/gdb: fix Linaro version stringYann E. MORIN"1-1/+1
Last update missed updating the version string. Signed-off-by: "Yann E. MORIN" <>
2011-04-28kernel/linux: add latest versionsYann E. MORIN"1-12/+17
Signed-off-by: "Yann E. MORIN" <>
2011-04-27config: small help fix up for work dir defaultYann E. MORIN"1-1/+1
Signed-off-by: "Yann E. MORIN" <>
2011-04-27debug/gdb: add latest Linaro versionYann E. MORIN"1-2/+2
Signed-off-by: "Yann E. MORIN" <>
2011-04-27debug/gdb: hide Linaro options by defaultYann E. MORIN"1-2/+25
It can be quite confusing for a new-comer to find strange version numbers for gdb, so hide the Linaro versions by default. Signed-off-by: "Yann E. MORIN" <>
2011-04-27cc/gcc: add latest Linaro versionsYann E. MORIN"1-6/+6
Signed-off-by: "Yann E. MORIN" <>
2011-04-27cc/gcc: suffle options aroundYann E. MORIN"2-65/+73
Move options around so it feels more organised. Add comments to separate groups of related options. Signed-off-by: "Yann E. MORIN" <>
2011-04-27config: reorder the kernels sub-menuYann E. MORIN"2-231/+232
Re-organise the sub-menu so that: - the kernels list comes first, - followed by kernels generic options - followed by kernels specific options Signed-off-by: "Yann E. MORIN" <>
2011-04-27config: reorder the architectures sub-menuYann E. MORIN"1-4/+4
Re-organise the sub-menu so that: - the archs list comes first, - followed by archs generic options - followed by archs specific options Signed-off-by: "Yann E. MORIN" <>
2011-04-20config/toolchain: hide sysroot name when in backend modeYann E. MORIN"1-1/+1
In backend mode, setting the sysroot name is the responsibility of the upper-layer build system. Signed-off-by: "Yann E. MORIN" <>
2011-04-16cc/gcc: add latest versionYann E. MORIN"1-0/+6
Propagate the gcc-4.4.5 patchset to the newly added gcc-4.4.6. Signed-off-by: "Yann E. MORIN" <>
2011-04-16kernel/linux: add latest versionsYann E. MORIN"1-39/+14
Signed-off-by: "Yann E. MORIN" <>
2011-04-06complibs: disable building shared libsYann E. MORIN"1-55/+0
Managing the shared version of the companion libraries has become cumbersome. Also, it will one day be possible to use the companion libraries from the host distribution, and then we will be able to easily use either shared or static libs. As a side note, while working on the canadian-rework series, it has become quite more complex to properly handle shared companion libraries, as they need to be built both for the build and gost systems. That's not easy to handle. At all. Signed-off-by: "Yann E. MORIN" <>
2011-04-04libc/glibc-common: force use of the BFD linkerYann E. MORIN"1-0/+6
gold can not build glibc/eglibc, force use of the BFD linker during the toolchain build. Reported-by: Bill Pringlemeir <> Signed-off-by: "Yann E. MORIN" <>
2011-04-04binutils/binutils: add blind option to force use of ld.bfd during buildYann E. MORIN"1-0/+8
gold is not capable of building glibc/eglibc, so we have to force using the BFD linker, ld.bfd. Offer a blind option that affected components can select to force use of the BFD linker during the build. Signed-off-by: "Yann E. MORIN" <>
2011-04-03binutils/binutils: warn if only gold is selectedYann E. MORIN"1-0/+5
gold is not capable of building glibc/eglibc. See this thread: Reported-by: Bill Pringlemeir <> Signed-off-by: "Yann E. MORIN" <>
2011-04-03binutils/binutils: always set name of the default linkerYann E. MORIN"1-7/+5
Always export the name of the default linker, even if only one of them is selected. Signed-off-by: "Yann E. MORIN" <>
2011-04-04binutils/binutils: hide gold option if no support for current architectureYann E. MORIN"1-1/+11
The gold linker does currently support only a limited set of architectures: - x86 (32- and 64-bit) - ARM Hide the gold option for other architectures. Signed-off-by: "Yann E. MORIN" <>
2011-04-03arch/sparc: add absic supportYann E. MORIN"1-0/+13
Add support for building SPARC targeted toolchain. With this patch I have built a working sparc V8 (32 toolchain). Testing shows that not all gcc versions works well: 4.4.1 OK (kernel builds and the final kernel can boot) 4.4.2 Not tested 4.4.3 Not tested 4.4.4 BAD (Kernel can build but fails during boot) 4.4.5 BAD (Kernel can build but fails during boot) 4.5.1 BAD (Build fails with a spill related ICE - 4.5.2 OK (kernel builds and boots) I have successfully been using the 4.5.2 version for a few months. This patch does not add support for the LEON variant. That may come later. Signed-off-by: Sam Ravnborg <> [ for 32-bit, default CT_TARGET_ARCH is OK] Signed-off-by: "Yann E. MORIN" <>
2011-03-28kernel/linux: update to latest versionsYann E. MORIN"1-6/+16
Signed-off-by: "Yann E. MORIN" <>
2011-03-27cc/gcc: fix linking with static PPL 0.11+Yann E. MORIN"1-0/+13
PPL 0.11+ installs three libs: lippl, libppl_c and libpwl. libppl_c has a dependency on libpwl (at least for watchdog stuff). While gcc correctly links with libppl and libppl_c, it does not pull libpwl in. In case of shared libs, this is not a problem, as libppl_c has a NEEDED dependency on libpwl. But for static libs, that does not work. Although exists and has a correct dependency on lipwl, somehow gcc misses it. So we have to force pulling libpwl when needed. Signed-off-by: "Yann E. MORIN" <>
2011-03-26cc/gcc: hide Linaro options by defaultYann E. MORIN"1-3/+21
It can be quite confusing for a new-comer to find strange version numbers for gcc, so hide the Linaro versions by default. Signed-off-by: "Yann E. MORIN" <>
2011-03-27cc/gcc: add linaro 4.6 pre-releaseYann E. MORIN"1-0/+7
Before gcc 4.6 was released, Linaro has a pre-release available. Include that version in the config list. Signed-off-by: "Yann E. MORIN" <>
2011-03-26cc/gcc: add 4.6.0Yann E. MORIN"1-0/+7
Signed-off-by: "Yann E. MORIN" <>
2011-03-19cc/gcc: prepare for upcoming 4.6Yann E. MORIN"2-1/+16
gcc 4.6 will no longer depend on libelf. Signed-off-by: "Yann E. MORIN" <>
2011-03-27cc/gcc: cleanup the _or_later logicYann E. MORIN"2-24/+48
So far, we've had a version always select appropriate _or_later option, which in turn would select all previous _or_later options. Because the dependencies on companion libs were cumulative, that was working OK. But the upcoming 4.6 will no longer depend on libelf, so we can't keep the cumulative scheme we've been using so far. Have each release family select the corresponding dependencies, instead of relying on selecting previous _or_later. Signed-off-by: "Yann E. MORIN" <>
2011-03-27cc/gcc: update linaro versionsYann E. MORIN"1-3/+3
Linaro has released version linaro-4.5-2011.03-0. Signed-off-by: "Yann E. MORIN" <>
2011-03-24kernel/linux: update versionYann E. MORIN"1-3/+3
Signed-off-by: "Yann E. MORIN" <>
2011-03-23kernel/linux: add altest versionYann E. MORIN"1-6/+16
Fix an incorrect version at the same time... :-( Signed-off-by: "Yann E. MORIN" <>
2011-03-22kernel/linux: add latest versionYann E. MORIN"1-3/+3
Signed-off-by: "Yann E. MORIN" <>
2011-03-17complibs/ppl: add latest versionYann E. MORIN"1-0/+6
Signed-off-by: "Yann E. MORIN" <>
2011-03-19kernel/linux: add newer versionsYann E. MORIN"1-3/+18
Signed-off-by: "Yann E. MORIN" <>
2011-02-27kernel/linux: add latest versionYann E. MORIN"1-0/+5
Signed-off-by: "Yann E. MORIN" <>
2011-02-22complibs/mpc: add latest version 0.9Yann E. MORIN"1-0/+6
Signed-off-by: "Yann E. MORIN" <>
2011-02-22complibs/ppl: add latest version 0.11.1Yann E. MORIN"1-0/+6
Signed-off-by: "Yann E. MORIN" <>
2011-02-22kernel/linux: fix typo in version stringYann E. MORIN"1-1/+1
Signed-off-by: "Yann E. MORIN" <>
2011-02-22cc/gcc: do not build plugins for static toolchainsYann E. MORIN"2-0/+2
Plugins are shared objects, and when building a toolchain statically, the gcc build system breaks havok (although there is no hard technical reasons it should not be possible)... And consequently, do not enable plugin supoprt in binutils. Reported-by: Thomas Spurden <> Signed-off-by: "Yann E. MORIN" <>
2011-02-21libc/glibc: LinuxThreads are no longer supported in latest versionsYann E. MORIN"1-1/+2
In fact, it is only supported in a few legacy versions. Keep LT available for all eglibc versions, although it might need a similar safeguard... Signed-off-by: "Yann E. MORIN" <>
2011-02-21libc/glibc: add fortify optionYann E. MORIN"1-0/+21
By default, recent versions of glibc and eglibc will build some functions that take format strings (eg. printf, syslog...) with run-time checks against some format string attacks. This is called a fortified build. Unfortunately, this fails somehow while building the instrumented version of syslog, with some kind of circular dependency... Disable fortified builds by default, and hide the enabling option behind EXPERIMENTAL for daring users... Signed-off-by: "Yann E. MORIN" <>
2011-02-21kernel/linux: add latest versionsYann E. MORIN"1-27/+17
... and remove old versions. Signed-off-by: "Yann E. MORIN" <>
2011-02-17debug/gdb: add versions from LinaroYann E. MORIN"1-0/+7
Signed-off-by: "Yann E. MORIN" <>
2011-02-17cc/gcc: add versions from LinaroYann E. MORIN"1-0/+15
Signed-off-by: "Yann E. MORIN" <>
2011-02-12libc/eglibc: Make eglibc 2.11 and 2.12 not experimentalBryan Hundven1-2/+0
I haven't noticed the usual experimental testers complain about eglibc 2.11 or 2.12 being unstable. So stop marking them as experimental. Signed-off-by: Bryan Hundven <>
2011-02-12libc/eglibc: Add 2.13 branchBryan Hundven1-0/+6
Signed-off-by: Bryan Hundven <>
2011-01-31libc/glibc: add option to force unwindYann E. MORIN"1-0/+15
We make it an option, as not all combinations of architectures vs. compiler vs. glibc/eglibc exhibit the issue. Mostly visible on old glibc versions, it seems... This is a missing part from the glibc/eglibc merger... :-/ Signed-off-by: "Yann E. MORIN" <>
2011-01-28cc/gcc: enable plugins if neededYann E. MORIN"2-0/+30
Enabling plugins in binutils is not enough, and gcc also needs to be ./configured with --enable-plugins, although this is not documented anywhere... :-/ Reported-by: karthik duraisami <> Signed-off-by: "Yann E. MORIN" <>
2011-01-28comptools: add make-3.81Yann E. MORIN"1-0/+5
Since the advent of make-3.82, some packages now break due to changes in make-3.82, being stricter than 3.81 when interpreting the Makefiles. This has bugged us a bit too much so far, and I believe fixing all of them is a long road, while simply building make-3.81 is the easiest route for now. Of course, in the long term, packages will get fixed upstream, and we should back-port the fixes to old versions, and get rid of building make-3.81. In the meantime... Reported several times on the mailing list. Signed-off-by: "Yann E. MORIN" <>
2011-01-28config: add an option not to remove the destination directoryYann E. MORIN"1-0/+22
In certain circumstances, removing the destination/installation directory is a bad idea. For example, when the build environment is already taking care of sanitising the build tree, and pre-installs stuff in there, it is a very bad idea to remove the destination directory. This happens now in buildroot, as the crostool-NG backend now installs the toolchain in the common host-tools directory, and pre-install there a few host-utilities (eg. host-automake and host-gawk). Provide a config knob to turn on/off the removal of the destination directory, defaulting to 'y' (previous behavior), and forced to 'n' when used as a backend. Reported-by: Peter Korsgaard <> Signed-off-by: "Yann E. MORIN" <>
2011-01-25config/toolchain: force use of sysroot if OBSOLETE is not setYann E. MORIN"1-0/+6
Use of the sysroot is highly recommended, and the non-sysroot case is both obsolete and not widely tested. Before the non-sysroot case can go away, deprecate it. Signed-off-by: "Yann E. MORIN" <>