summaryrefslogtreecommitdiff
path: root/toolchain
AgeCommit message (Collapse)Author
2010-08-29uClibc: fix ppc e500 handlingStanislav Bogatyrev
Closes #2449 Signed-off-by: Stanislav Bogatyrev <bogatyrev_stanislav@gmail.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-08-25toolchain/gcc: fix 4.2.4 build after uClibc NTPL support got addedKhem Raj
Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-08-24Bump stable kernel headersGustavo Zacarias
Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
2010-08-11Prevent C++ + locale + uClibc 0.9.31 + gcc 4.2 to be selectedThomas Petazzoni
The problem fixed by 60f945e47a15e10f0e777f69b05492b6f7ba918d is in fact not limited to the AVR32 architecture, as reported by Will Newton on the list. The issue is the combination uClibc 0.9.31 with gcc 4.2, C++ support and locales. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-08-11Add the traditional powerpc-link-with-math-lib patch to gcc 4.4.4Thomas Petazzoni
Patch taken from Crosstool-NG patchset. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-08-11Detect early if an UTF-8 locale is neededThomas Petazzoni
Check in toolchain/dependencies/dependencies.sh if an UTF-8 locale is properly present on the system before trying to build a locale enabled toolchain. As this test is only needed when a locale enabled toolchain is going to be built, we pass the configuration file path to the dependencies.sh script so that it can grep for the current value of various options. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-08-11Make uClibc gen_wc8bit shows an error when no locale support availableThomas Petazzoni
When no UTF-8 locale is available on the host system, uClibc can't generate some stuff it needs to compile a C library with locale support. Unfortunately, as gen_wc8bit message is shown on stdout and the stdout of gen_wc8bit is redirected to a file, the user don't see anything, as reported at http://lists.busybox.net/pipermail/buildroot/2010-May/034177.html. Those two patches fix the problem for uClibc 0.9.31 and 0.9.30.3. It has been submitted upstream: http://lists.uclibc.org/pipermail/uclibc/2010-August/044256.html Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-07-30Merge branch 'fixes-20100729' of git://git.busybox.net/~tpetazzoni/git/buildrootPeter Korsgaard
2010-07-30gcc: move <tuple>/lib* symlink handling up to gcc-intermediatePeter Korsgaard
The <tuple>/lib* symlinking added by 3c77bab2eeace needs to be moved up to the gcc-intermediate step now the NPTL stuff is merged, otherwise 64bit builds fails (lib64 already created). Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-07-30toolchain: enforce --disable-multilibPeter Korsgaard
Since 5575d205c (toolchain: remove multilib) we were no longer passing --disable-multilib, which broke builds for multilib-capable archs (like x86-64, ppc, ..). Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-07-29toolchain: mark uClibc 0.9.31 + locale + C++ as brokenThomas Petazzoni
It fails to build with: ctype_members.cc: In constructor 'std::ctype_byname<_CharT>::ctype_byname(const char*, size_t) [with _CharT = char]': ctype_members.cc:59: error: invalid use of incomplete type 'struct __uclibc_locale_struct' /home/test/avr32-br/usr/avr32-unknown-linux-uclibc/sys-include/bits/uClibc_locale.h:85: error: forward declaration of 'struct __uclibc_locale_struct' ctype_members.cc:60: error: invalid use of incomplete type 'struct __uclibc_locale_struct' /home/test/avr32-br/usr/avr32-unknown-linux-uclibc/sys-include/bits/uClibc_locale.h:85: error: forward declaration of 'struct __uclibc_locale_struct' ctype_members.cc:61: error: invalid use of incomplete type 'struct __uclibc_locale_struct' /home/test/avr32-br/usr/avr32-unknown-linux-uclibc/sys-include/bits/uClibc_locale.h:85: error: forward declaration of 'struct __uclibc_locale_struct' make[5]: *** [ctype_members.lo] Error 1 Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-07-29uClibc: remove old 0.9.28 supportPeter Korsgaard
Not supported upstream and needs complicated workaround for the NPTL stuff. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-07-29gcc-4.2.4: Add patch to accept --with-abi=aapcs-linuxKhem Raj
Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-07-29Add support for uclibc NPTL toolchain.Khem Raj
This patch modifies current toolchain build sequence so that NPTL enabled toolchain can be built. The new sequence works well with linuxthreads as well. It introduces a new pass for gcc cross compilation. The new sequence is binutils->gcc-initial->linux-headers -> uclibc-configured (some cheats to generate phony shared libc.so and libm.o) -> gcc-intermediate(with shared lib support) -> uclibc -> gcc-final I also added a new sample config arm_nptl_toolchain_defconfig which builds the toolchain and busybox. I have only tried it on arm. However it should work for other architectures which support NPTL on uclibc e.g. mips, sh, x86, ppc, x86_64 Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-07-29gdb: disallow GDB_HOST on external toolchain buildsThomas Petazzoni
The cross-gdb is supposed to be part of the external toolchain, so Buildroot does not need to build it. Moreover, GDB_HOST build currently fail with: ln -snf ../../bin/arm-unknown-linux-gnueabi-gdb \ /home/test/outputs/test-48/staging/usr/arm-unknown-linux-gnueabi/bin/gdb ln: creating symbolic link `/home/test/outputs/test-48/staging/usr/arm-unknown-linux-gnueabi/bin/gdb': No such file or directory And even worse: they overwrite the cross-gdb of the external toolchain! Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-07-29dependencies: add svn as a mandatory toolThomas Petazzoni
Now that two packages (tremor and libsvgtiny) are being downloaded from svn, svn becomes a mandatory tool to run Buildroot. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-07-28toolchain: remove multilibThomas Petazzoni
Supporting multilib is much more than just passing --enable-multilib to gcc. You have to actually build the C library several times (once for each multilib variant you want to support in your toolchain), and to pass MULTILIB_OPTIONS/MULTILIB_EXCEPTIONS values to gcc to let it know the set of multilib variants you're interested in. Since we'll probably never support multilib toolchains in Buildroot, just get rid of this BR2_ENABLE_MULTILIB option. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-07-28gcc: remove option on SJLJ exceptionsThomas Petazzoni
This is a very advanced option, and it seems, according to http://choices.cs.uiuc.edu/exceptions.pdf that SJLJ exceptions aren't really interesting. Users really interested by this can always use the BR2_EXTRA_GCC_CONFIG_OPTIONS is they want. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-07-28toolchain: move buildroot config filesYann E. MORIN
Handle the internal toolchain backend mechanism the same way we handle other backends. Signed-off-by: Yann E. MORIN <yann.morin.1998@anciens.enib.fr> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-07-28toolchain: move makefile includesYann E. MORIN
Including a bunch of Makefiles with wildcard makes it impossible to add new toolchain backends. Avoid that by namely including needed files. The external toolchain still needs to include all the toolchain/*/*.mk sub-makefiles, as they are needed to build a toolchain that runs on the target. It is to be noted that the cross-toolchain is not built in this case, as the make-targets to build the cross-toolchain are not present in the $(BASE_TARGETS) variable, which is later used to create the dependency rules. Also, the comment 'Explicit ordering' has been removed, as it is mis- leading. It is make's responsibility to create the proper ordering based on the dependency rules it finds in the Makefiles Signed-off-by: Yann E. MORIN <yann.morin.1998@anciens.enib.fr> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-07-28toolchain: rename external toolchain dirYann E. MORIN
Rename the external toolchain directory. When new backends are here, it will be easier to sort them out if they are all prefixed the same way. Signed-off-by: Yann E. MORIN <yann.morin.1998@anciens.enib.fr> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-07-28toolchain: move helper functions from external toolchainYann E. MORIN
The helper functions used for external toolchains may also be useful to alternate toolchain backends (currently, the external toolchain is the sole user). Signed-off-by: Yann E. MORIN <yann.morin.1998@anciens.enib.fr> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-07-27Merge branch 'avr32-toolchain-fix' of ↵Peter Korsgaard
git://git.busybox.net/~tpetazzoni/git/buildroot
2010-07-27toolchain: remove redundant and incorrect --with-build-time-tools optionThomas Petazzoni
This option is already part of the gcc configure options through the BR2_CONFIGURE_BUILD_TOOLS variable (in toolchain/Makefile.in). Additionnally, the value that was passed in the AVR32 specific case was incorrect: it was $(STAGING_DIR)/$(REAL_GNU_TARGET_NAME)/bin instead of $(STAGING_DIR)/usr/$(REAL_GNU_TARGET_NAME)/bin. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-07-27toolchain: Remove now-unused variablesThomas Petazzoni
The variable BR2_SYSROOT_STAGING_DESTDIR is no longer used, since now the prefix for gcc is already set to the correct location. The variable BR2_SYSROOT_TARGET_DESTDIR was already unused. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-07-27binutils,gcc: use correct --prefixThomas Petazzoni
The cross binutils and cross gcc are actually going to be executed from $(STAGING_DIR)/usr, so the correct prefix is $(STAGING_DIR)/usr and not /usr. This also fixes what is known as the "AVR32 toolchain build failure", which was due to the fact that the prefix directory wasn't writable (since it was /usr). Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-07-27Merge branch 'various-bumps' of git://git.busybox.net/~tpetazzoni/git/buildrootPeter Korsgaard
2010-07-27Create <tuple>/lib -> <sysroot>/lib symlink before installing cross gccThomas Petazzoni
This commit solves bug #1051. The problem in this bug in that WebKit compiles a sample C program, which uses WebKit. As WebKit is written in C++, even though the program it built with CROSS-gcc, it must be linked with libstdc++. However, CROSS-gcc can't find the libstdc++ has it's hidden inside <sysroot>/<tuple>/lib. Therefore, this commit creates a symbolic link <sysroot>/<tuple>/lib -> <sysroot>/lib before running the CROSS-gcc installation. While this may look like a hack, this is the solution used by both Crosstool-NG and OpenWRT. Moreover, with this symbolic link in place, I think bug #1741 may also be solved. The problem in this bug is that the linker tries to link against /lib/libc.so.0. This is due to the fact that the linker finds a libc.so script file in the original toolchain location and not inside the copy of the toolchain sysroot in $(STAGING_DIR). As the script file is found outside of the current toolchain sysroot, ld considers the script has non-sysrooted, and therefore doesn't prefix all paths found in the script file (such as /lib/libc.so.0) with the sysroot path, leading to the failure. So, in details, this commit : * Adds a BR2_ARCH_IS_64 invisible config knob that is used to know if the arch is a 64 bits architecture or not. * Creates the <sysroot>/<tuple>/lib -> <sysroot>/lib symbolic link, and the <sysroot>/<tuple>/lib64 -> <sysroot>/lib64 symbolic link if needed. * Fixes the external toolchain sysroot detection code so that the 'sed' replacement is done *after* the readlink -f evaluation. I have tested this by building ARM, x86 and x86_64 toolchains with Buildroot, and then use these toolchains as external toolchains to build a full X.org/Gtk/WebKit/Midori stack. I have also done a complete ARM Buildroot internal toolchain build with the same full X.org/Gtk/WebKit/Midori stack. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-07-27target-g++: fix buildThomas Petazzoni
Just as we did to fix target-gcc, pass CXX_FOR_TARGET when building target g++, and remove useless copies of g++ and c++. Tested on ARM by compiling a simple C++ program using <iostream> on the target and running it. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-07-27target-gcc: remove useless copies of gccThomas Petazzoni
When doing the "make install" of target, three identical copies of gcc are installed in $(TARGET_DIR)/usr/bin: 039adcc582c365f12ba6fc5f96098128 arm-unknown-linux-uclibcgnueabi-gcc 039adcc582c365f12ba6fc5f96098128 arm-unknown-linux-uclibcgnueabi-gcc-4.3.5 039adcc582c365f12ba6fc5f96098128 gcc This patch removes the first two copies and keeps only the common "gcc" one. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-07-27target-gcc: no need to strip binaries, remove .la files and docThomas Petazzoni
This is done in a global way by the target-finalize target of the main Makefile. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-07-27target-gcc: fix buildThomas Petazzoni
Now that $(STAGING_DIR)/usr/bin is no longer in the PATH, we need to pass the absolute paths to $(TARGET_CC) when building the target gcc compiler. This commit fixes the target gcc build problem reported on the list. I have successfully been able to build a target gcc for ARM, use it to compile a hello world application on the target and run this application. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-07-27target-gcc: Get rid of TARGET_GCC_FLAGSThomas Petazzoni
This variable is used only once, so let's just hardcode its value at its call site. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-07-26java: mark as brokenPeter Korsgaard
We haven't had any updates to the java packages in a long time, gcj in 4.3.x doesn't build, and 4.4.x is missing ecj1, so it cannot have many users. Mark it as broken and remove during the 2010.11 cycle, unless someone steps up to maintain it. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-07-13sstrip: fix section length corruption bugPeter Korsgaard
Based on openwrt #6847: https://dev.openwrt.org/ticket/6847 Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-07-09toolchain/gcc: cleanup softfloat selectionPeter Korsgaard
We don't have a BR2_SOFT_FLOAT_FP option, and -mfloat-abi should also be used for big endian ARM. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-07-08ext-toolchains: fix libnss_*.so installation with external glibcLuca Ceresoli
Commit 7192668 introduced a wrong spelling of BR2_TOOLCHAIN_EXTERNAL_GLIBC that prevented libnss_files.so and libnss_dns.so from being installed. Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-07-08Merge branch 'misc-fixes' of git://git.busybox.net/~tpetazzoni/git/buildrootPeter Korsgaard
2010-07-07GETPT support is needed by rxvt.Darius Augulis
Signed-off-by: Darius Augulis <augulis.darius@gmail.com>
2010-07-07Update all packages to quote $(TARGET_CC)Thomas Petazzoni
Now that TARGET_CC contains several space-separated words, it must be used quoted everywhere. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-07-07external-toolchain: adjust tests on TARGET_CC and TARGET_CXXThomas Petazzoni
Following the changes to TARGET_CC/TARGET_CXX to include the --sysroot option, these variables not only contain the path to the compiler, but also the --sysroot option. For that reason, we cannot anymore just use "test -x" to test for the compiler presence. Instead, we see if $(TARGET_CC) -v and $(TARGET_CXX) -v return a zero status. Moreover, --sysroot now needs to be filtered out of $(TARGET_CC) and not $(TARGET_CFLAGS) when asking the toolchain for its original sysroot and arch sysroot. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-07-07Rework sysroot option handlingThomas Petazzoni
The external toolchain and internal toolchain cases both need to use the --sysroot option, and they have almost identical LDFLAGS/CFLAGS/CXXFLAGS definition, so we can factorize these definitions. Moreover, the --isysroot option is implied by --sysroot so there's no need to specify both. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-07-06uClibc: workaround 0.9.31 / GCC PR32219 issue with static linkingPeter Korsgaard
Closes #2143 Fixes crash on static linking without stdio / x86. Both patches are from upstream uClibc. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-07-06external-toolchain: hardcode the destination directory for a libraryThomas Petazzoni
Until now, the function copy_toolchain_lib_root was copying a given library to the target filesystem by assuming that it should be at the same place it was in the toolchain sysroot. However, with Buildroot hiding libstdc++ in /usr/<target-name>/lib(64), this isn't correct, and it is probably safer not to rely on the toolchain organization anyway. Therefore : * Instead of having a single EXTERNAL_LIBS variable, we now have LIB_EXTERNAL_LIBS and USR_LIB_EXTERNAL_LIBS, which respectively list the libraries that should be copied to /lib and /usr/lib. As of today, only libstdc++ is part of the second list. * The copy_toolchain_lib_root takes another argument, which is the destination directory of the library, relative to $(TARGET_DIR) Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-07-06external-toolchain: handle libstdc++/libgcc_s for BR toolchainsThomas Petazzoni
Most toolchains have their libraries either in /lib or /usr/lib relative to their ARCH_SYSROOT_DIR. Buildroot toolchains, however, have basic libraries in /lib, and libstdc++/libgcc_s in /usr/<target-name>/lib(64). Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-07-06uclibc: add patch to fix fcntl64() on 64 bits targetsThomas Petazzoni
The patch is already in upstream uClibc, in the master branch, at http://git.buildroot.net/uClibc/commit/?id=6f1daaaf2d94c1e6184add44eda38b0781b88cf0. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-07-06external-toolchain: recognize uClibc 64 bits toolchainsThomas Petazzoni
With uClibc 64 bits toolchain, the dynamic loader is named ld64-uClibc.so.0 and not ld-uClibc.so.0. So, this commit adjust the uClibc detection code for external toolchains. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: Yann E. MORIN <yann.morin.1998@anciens.enib.fr> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-07-06external-toolchain: mention MIPS and PowerPC CodeSourcery toolchainsThomas Petazzoni
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-07-06external-toolchain: create lib64 symlinks if neededThomas Petazzoni
Create lib64 -> lib and usr/lib64 -> usr/lib symbolic links in the target and staging directories. This is needed for some 64 bits toolchains such as the Crosstool-NG toolchains, for which the path to the dynamic loader and other libraries is /lib64, but the libraries are stored in /lib. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: Yann E. MORIN <yann.morin.1998@anciens.enib.fr> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-07-06external-toolchain: support 64 bits glibc toolchainsThomas Petazzoni
On 64 bits glibc toolchains, the dynamic loader is named ld-linux-x86-64.so and not simply ld-linux.so. So, adjust the detection of the C library accordingly. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-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-14 23:00:33 +0000