summaryrefslogtreecommitdiff
path: root/config
AgeCommit message (Collapse)AuthorFilesLines
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 - http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35664) 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 <sam@ravnborg.org> [yann.morin.1998@anciens.enib.fr: for 32-bit, default CT_TARGET_ARCH is OK] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-03-28kernel/linux: update to latest versionsYann E. MORIN"1-6/+16
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
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 libppl_c.la 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" <yann.morin.1998@anciens.enib.fr>
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" <yann.morin.1998@anciens.enib.fr>
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" <yann.morin.1998@anciens.enib.fr>
2011-03-26cc/gcc: add 4.6.0Yann E. MORIN"1-0/+7
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
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" <yann.morin.1998@anciens.enib.fr>
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" <yann.morin.1998@anciens.enib.fr>
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" <yann.morin.1998@anciens.enib.fr>
2011-03-24kernel/linux: update versionYann E. MORIN"1-3/+3
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
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" <yann.morin.1998@anciens.enib.fr>
2011-03-22kernel/linux: add latest versionYann E. MORIN"1-3/+3
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-03-17complibs/ppl: add latest versionYann E. MORIN"1-0/+6
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-03-19kernel/linux: add newer versionsYann E. MORIN"1-3/+18
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-02-27kernel/linux: add latest 2.6.37.2 versionYann E. MORIN"1-0/+5
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-02-22complibs/mpc: add latest version 0.9Yann E. MORIN"1-0/+6
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-02-22complibs/ppl: add latest version 0.11.1Yann E. MORIN"1-0/+6
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-02-22kernel/linux: fix typo in version stringYann E. MORIN"1-1/+1
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
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 <thomas@ado.is-a-geek.net> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
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" <yann.morin.1998@anciens.enib.fr>
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" <yann.morin.1998@anciens.enib.fr>
2011-02-21kernel/linux: add latest versionsYann E. MORIN"1-27/+17
... and remove old versions. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-02-17debug/gdb: add versions from LinaroYann E. MORIN"1-0/+7
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-02-17cc/gcc: add versions from LinaroYann E. MORIN"1-0/+15
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
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 <bryanhundven@gmail.com>
2011-02-12libc/eglibc: Add 2.13 branchBryan Hundven1-0/+6
Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
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" <yann.morin.1998@anciens.enib.fr>
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 <kdconstant@hotmail.com> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
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" <yann.morin.1998@anciens.enib.fr>
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 <jacmet@sunsite.dk> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
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" <yann.morin.1998@anciens.enib.fr>
2011-01-25config: add an option to name the sysroot directoryYann E. MORIN"1-2/+15
Depending on local policies, some users have expressed a need to have the sysroot be named differently than the hard-coded name. Add an option for that. Default to 'sysroot' to match the existing literature. While at it, replace 'sys-root' with 'sysroot' everywhere we reference the sysroot. Reported-by: Alexey Kuznetsov <Alexey.KUZNETSOV@youtransactor.com> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-01-03libc-glibc: remove 2.3.6Yann E. MORIN"1-6/+0
This is an obsolete version which is no longer used by any sample (the only user, the ia64 sample, has been removed). It also makes the code path a bit complex, with twists just to accomodate that version. Removing the version will make those twists go away, and will ease commonalisation of glibc and eglibc in the future (hopefully!). Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-01-03arch: remove ia64Yann E. MORIN"1-11/+0
ia64 is broken in every gcc/glibc combinations I tested (except for the existing sample that used very old versions). Nobody complained on the list about not being able to build recent versions. So the only way forward I can see is to remove the architecture altogether. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-01-08kernel/linux: add latest versionsYann E. MORIN"1-6/+16
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2010-12-29binutils/binutils: add wrapper to gold and ldYann E. MORIN"1-0/+24
When both gold and ld are installed, add a wrapper that calls to either gold or ld. In case the wrapper is installed, we also need to symlink ld.bfd and ld.gold for the core_cc steps. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-01-02binutils/binutils: add support for threaded goldYann E. MORIN"1-0/+8
When configured with support for threads, gold can link in parallel, possibly cooperating with a make jobserver. Add an option enabling threads. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-01-02binutils/binutils: add support for pluginsYann E. MORIN"1-0/+13
Add an option to enable plugins support in binutils. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2010-12-27binutils/binutils: add option to enable goldYann E. MORIN"1-0/+66
gold is a new, optimised, multi-threaded linker with support for plugins. Add support for gold starting with binutils 2.21. Although 2.20 also had gold, the configure flags have changed, and supporting 2.20 would be a mess in the code. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2010-12-28binutils/binutils: add BINUTILS_2_21_or_later blind optionYann E. MORIN"1-0/+4
Add BINUTILS_2_21_or_later blind option. It will be used to add conditional support for building 'gold' on versions that have it. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-01-02libc/eglibc: normalize eglibc hidden version namesBryan Hundven1-20/+20
In the previous patches to glibc and uclibc, we standardized on hidden version names: LIBC_<LIBC NAME>_V_<VERSION> This patch updates EGLIBC to be the same for consistency to: LIBC_EGLIBC_V_<VERSION> Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
2011-01-03libc/uClibc: normalize uclibc hidden version namesBryan Hundven1-12/+12
Hidden version names for uClibc conflicted: LIBC_UCLIBC_V_0_9_30_2 LIBC_V_0_9_30_1 name them constantly as: LIBC_UCLIBC_V_<version> Also update the build script where we use snapshots by version or snapshots by date. Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
2011-01-02libc/glibc: normalize glibc hidden version namesBryan Hundven1-18/+18
Hidden version names for glibc conflicted: LIBC_GLIBC_V_2.10.1 LIBC_V_2.10 name them constantly as: LIBC_GLIBC_V_<version> Reported-by: Esben Haabendal <eha@doredevelopment.dk> Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
2010-12-29libc/glibc: add 2.12.1 and 2.12.2Heiko Zuerker1-0/+12
Signed-off-by: Heiko Zuerker <heiko@zuerker.org>
2010-12-29cc/gcc: Add gcc 4.5.2Bryan Hundven1-0/+7
Add gcc 4.5.2. Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
2010-12-21docs: overview.txt is gone, point to the new documentationYann E. MORIN"3-8/+9
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2010-12-14config/binutils: Add binutils 2.21Bryan Hundven1-0/+6
Currently depends on EXPERIMENTAL, as it is not well tested and I'm not sure if/which patches need to be ported forward from 2.20.1.
2010-12-18config: fix the patch fallbacks methodsYann E. MORIN"1-2/+2
Reported-by: Heiko Zuerker <heiko@zuerker.org> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2010-12-18kernel/linux: fix help for 2.6.35.10Yann E. MORIN"1-0/+1
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2010-12-17kernel/linux: bump to latest versionsYann E. MORIN"1-15/+37
- add 2.6.36.2. - bump to 2.6.35.10, which is a new longterm. - bump to 2.6.32.27 and 2.6.27.57, the two old longterms. - update longterm descriptions. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
generated by cgit v0.10.2-6-g49f6 at 2024-04-24 08:14:14 (GMT)