summaryrefslogtreecommitdiffstats
path: root/toolchain/gcc/gcc-uclibc-4.x.mk
Commit message (Collapse)AuthorAgeFilesLines
* gcc: move <tuple>/lib* symlink handling up to gcc-intermediatePeter Korsgaard2010-07-301-7/+5
| | | | | | | | 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>
* toolchain: enforce --disable-multilibPeter Korsgaard2010-07-301-0/+4
| | | | | | | | 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>
* Add support for uclibc NPTL toolchain.Khem Raj2010-07-291-28/+102
| | | | | | | | | | | | | | | | | | | | 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>
* toolchain: remove multilibThomas Petazzoni2010-07-281-4/+1
| | | | | | | | | | | | | 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>
* gcc: remove option on SJLJ exceptionsThomas Petazzoni2010-07-281-2/+0
| | | | | | | | | | | 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>
* Merge branch 'avr32-toolchain-fix' of ↵Peter Korsgaard2010-07-271-2/+2
|\ | | | | | | git://git.busybox.net/~tpetazzoni/git/buildroot
| * binutils,gcc: use correct --prefixThomas Petazzoni2010-07-271-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | 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>
* | Merge branch 'various-bumps' of git://git.busybox.net/~tpetazzoni/git/buildrootPeter Korsgaard2010-07-271-2/+6
|\ \ | |/ |/|
| * Create <tuple>/lib -> <sysroot>/lib symlink before installing cross gccThomas Petazzoni2010-07-271-2/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* | target-g++: fix buildThomas Petazzoni2010-07-271-1/+4
| | | | | | | | | | | | | | | | | | | | 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>
* | target-gcc: remove useless copies of gccThomas Petazzoni2010-07-271-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* | target-gcc: no need to strip binaries, remove .la files and docThomas Petazzoni2010-07-271-9/+0
| | | | | | | | | | | | | | 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>
* | target-gcc: fix buildThomas Petazzoni2010-07-271-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* | target-gcc: Get rid of TARGET_GCC_FLAGSThomas Petazzoni2010-07-271-1/+4
|/ | | | | | | 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>
* toolchain: remove unused special detection of old toolchainsPeter Korsgaard2010-07-021-29/+1
| | | | | | We only support gcc >= 4.2.x for the internal toolchain. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* toolchain: remove gcc 4.1.2 and non-sysroot supportPeter Korsgaard2010-06-151-12/+1
| | | | Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* gmp/mpfr: make sure host builds add source targets to HOST_SOURCEPeter Korsgaard2010-02-251-0/+1
| | | | | | | | | | | | | | Closes #1183. When gmp/mpfr is needed for the host (E.G. when using an internal toolchain), the host-lib{gmp,mpfr}-source targets weren't added to HOST_SOURCE, so make source / external-deps didn't handle them. Notice that we have the same issue with the new host package support, there we should probably use HOST_<package>_DEPENDENCIES for -source dependencies. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* gcc on target: add missing definitions for gcc 4.4Thomas Petazzoni2010-02-251-0/+4
| | | | | | | | | Depending on the gcc version, the gcc include and lib directories have changed. We include support for gcc 4.4 by copy/pasting the support for gcc 4.3. Locations don't seem to have changed between 4.3 and 4.4. This allows the syslimits.h fixup to succeed. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* gcc: do not pass --with-pkgversion to gcc < 4.3Thomas Petazzoni2009-12-151-1/+1
| | | | | | | | | | | | | | | | | Commit 09c181f2891276c458de327d241151bab38bde0f added new options passed to gcc configure to set --with-pkgversion and --with-bugurl, to gcc >= gcc 4.3. To check this, it was checking that the GCC_VERSION string does not contain 4.2. Unfortunately, the test is bogus. It does a findstring on x4.2. (with a final dot) but compares the result with x4.2 (without the final dot). The result is that even with 4.2 versions, the test was true, leading --with-pkgversion and --with-bugurl being passed to gcc's configure script. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* Merge branch 'remove-external-toolchain' of ↵Peter Korsgaard2009-12-151-30/+11
|\ | | | | | | git://git.busybox.net/~tpetazzoni/git/buildroot
| * gcc: remove GCC_OFFICIAL_VERSION and just use GCC_VERSION insteadThomas Petazzoni2009-12-141-17/+4
| | | | | | | | Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
| * gcc: remove support for external source toolchainsThomas Petazzoni2009-12-141-10/+0
| | | | | | | | Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
| * gcc: add avr32 special versionThomas Petazzoni2009-12-141-6/+10
| | | | | | | | | | | | | | | | | | | | | | | | * Add new gcc version 4.2.2-avr32-2.1.5 in Config.in * Select the Atmel mirror to download gcc with avr32 in their version name, in gcc-uclibc-*.mk * Do not apply patches if the patch directory is empty, in gcc-uclibc-*.mk Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* | gcc: remove hurd specific detailsThomas Petazzoni2009-12-141-4/+0
|/ | | | Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* Add pkgversion to gcc >= 4.3Gustavo Zacarias2009-12-061-0/+7
| | | | | | | | Closes #765. [Peter: change to check for !4.2.x instead] Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* buildroot: silence ./configure step when building with 'make -s'Peter Korsgaard2009-10-011-3/+3
| | | | | | | | | | We have been passing -q to ./configure when using 'make -s' for packages using Makefile.autotools.in for some time. Do the same for packages using autotools, but not using the Makefile.autotools.in infrastructure, taking care to not do it for packages with hand written configure scripts. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* Add a config option for gcc tls support, rather than disabling it blindlyAustin Foxley2009-09-231-3/+9
| | | | | | | | Defaulted to yes, but blocked it from gcc 4.4.x since the disable was originally added because of problems with its c++ support reportedly. Signed-off-by: Austin Foxley <austinf@cetoncorp.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* rename TOOL_BUILD_DIR to TOOLCHAIN_DIRMichael Roth2009-09-231-6/+6
| | | | | | | | To reflect the new output directory hierachy rename the Makefile variable TOOL_BUILD_DIR to TOOLCHAIN_DIR. Signed-off-by: Michael Roth <mroth@nessie.de> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* Remove the "project" featureThomas Petazzoni2009-09-161-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The "project" feature was designed to allow to several projects to be built inside the same Buildroot source tree and allowing the toolchain and non-configurable packages to be shared between the different projects on the same architecture. While being interesting in theory, this feature adds a level of complexity to Buildroot, both from an user perspective and from a developer perspective, while one of the main Buildroot strengh is to be simple. Moreover, this feature is only seldomly used by our users. From a user-level perspective, this for example allows to remove the project_build_ARCH directory, which was very confusing. The autotools-stamps directory is also removed, since these stamps are back at their normal location. Description of the changes involved : * project/, directory removed * Makefile - Don't include project/Makefile.in and project/project.mk anymore - Grab a copy of the contents of project/Makefile.in at the location it was imported, but remove the definition related to PROJECT_BUILD_DIR. The TARGET_DIR is now in $(BUILD_DIR)/target_dir - Remove the creation/removal of the $(PROJECT_BUILD_DIR) and $(PROJECT_BUILD_DIR)/autotools-stamps directories - Don't make world depends on target-host-info. This target was defined by project/project.mk to customize /etc/issue, /etc/hostname and create /etc/br-version depending on the project definitions. We can of course imagine re-adding such a feature later. - Replace PROJECT_BUILD_DIR by BUILD_DIR everywhere - Remove the update, log and lognr.$(PROJECT) target, they were specific to the project feature. * package/Makefile.autotools.in - Replace PROJECT_BUILD_DIR by BUILD_DIR for the location of the configure cache - Move the INSTALL_TARGET and HOOK_POST_INSTALL stamps to the same directory as the other stamps (i.e, in the package directory). * package/Makefile.in - Replace PROJECT_BUILD_DIR by BUILD_DIR for the location of the configure cache * package/at/at.mk, package/busybox/busybox.mk, package/busybox/initramfs.mk, package/customize/customize.mk, package/linux-fusion/linux-fusion.mk, package/ltp-testsuite/ltp-testsuite.mk, package/nfs-utils/nfs-utils.mk, target/cpio/cpioroot.mk, target/cramfs/cramfs.mk, target/device/Atmel/DataFlashBoot/DataflashBoot.mk, target/device/Atmel/Makefile.in, target/device/Atmel/at91bootstrap/at91bootstrap.mk, target/device/KwikByte/Makefile.in, target/ext2/ext2root.mk, target/initramfs/initramfs.mk, target/iso9660/iso9660.mk, target/jffs2/jffs2root.mk, target/linux/Makefile.in, target/romfs/romfs.mk, target/squashfs/squashfsroot.mk, target/tar/tarroot.mk, target/ubifs/ubifsroot.mk - Replace PROJECT_BUILD_DIR by BUILD_DIR * target/device/Config.in - Do not include project/Config.in anymore * target/linux/Makefile.in.advanced - Replace PROJECT_BUILD_DIR by BUILD_DIR - Store the stamps file in $(STAMP_DIR) instead of $(PROJECT_BUILD_DIR)/autotools-stamps * target/u-boot/Makefile.in - Replace PROJECT_BUILD_DIR by BUILD_DIR - Remove $(PROJECT) from the U-Boot target binary name - Remove the insertion in the configuration of the project name as the hostname - The u-boot-autoscript target now generates $(U_BOOT_AUTOSCRIPT).img instead of $(U_BOOT_AUTOSCRIPT).$(PROJECT) * toolchain/gcc/gcc-uclibc-3.x.mk toolchain/gcc/gcc-uclibc-4.x.mk - Move the stamps files to $(STAMP_DIR) Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* toolchain: xtensa toolchain patch supportMaxim Grigoriev2009-07-241-1/+6
| | | | | | | Part of #163. Signed-off-by: Maxim Grigoriev <maxim2405@gmail.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* toolchain/gcc: ensure libraries are copied to target_dir for x86-64Peter Korsgaard2009-07-021-3/+3
| | | | | | | | x86-64 stores libgcc_s / libstdc++ / libgcj under lib64 instead of lib, so make sure that directory is searched as well for libraries to copy to target. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* gcc-4.3.3: add a patch to link with the math lib to get copysignalAngus Salkeld2009-05-121-0/+5
| | | | | | | | | | | Conditionally apply the following patch by Bernhard Reutner-Fischer which solves a link error on powerpc (with softfloat or multilib) when using a shared libgcc_s. See: http://gcc.gnu.org/ml/gcc-patches/2008-10/msg00237.html http://www.nabble.com/PPC-won't-build-with-soft-float-td22772110.html Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* toolchain/gcc: fix java supportPeter Korsgaard2009-04-271-5/+5
| | | | Not runtime tested, but now it atleast builds.
* toolchain/gcc: disable tls supportPeter Korsgaard2009-04-271-0/+3
| | | | Fixes libstdc++ linking with gcc 4.4.x
* toolchain/gcc: don't enable libssp supportPeter Korsgaard2009-04-221-0/+3
| | | | | It's broken anyway as we don't install libssp* into TARGET_DIR, and we should use the SSP support in uClibc if we want stack protection.
* toolchain/gcc: libstdcpp dependency was listed twicePeter Korsgaard2009-03-011-1/+0
|
* toolchain: revert r25193 (Change binary toolchain configuration)Peter Korsgaard2009-02-041-18/+0
| | | | As discussed on the list.
* Change binary toolchain configuration, soUlf Samuelsson2009-01-311-0/+18
| | | | | | | | | | | that the options become visible just below the config, instead of at bottom of screen Create a more useful default as toolchain path. Allow generation of a script which sets up paths to a binary toolchain generated by buildroot.
* toolchain: fix up GNU_TARGET_NAME link and target_utils locationPeter Korsgaard2009-01-301-4/+4
| | | | | | The GNU_TARGET_NAME symlink and target_utils location were not correctly adjusted to match the move of the toolchain to $(STAGING_DIR)/usr, creating dangling symlinks.
* toolchain/gcc: remove unused gcc 3.x cruft from 4.x makefile (sysroot)Peter Korsgaard2009-01-301-42/+2
|
* toolchain/gcc: remove ancient (and unused) i386 softfloat patchPeter Korsgaard2009-01-291-4/+0
|
* toolchain/gcc: remove unused GCC_ENABLE_CLOCALEPeter Korsgaard2009-01-291-4/+0
| | | | | | | This variable was introduced in r17046 (add gfortran support, 2006-12-22) and wasn't used even there. Signed-off-by: Markus Heidelberg <markus.heidelberg@web.de>
* toolchain/gcc: make version detection more robustPeter Korsgaard2009-01-221-8/+8
| | | | | Thanks to Bernhard for noticing (and less so for causing the problem in the first place :P)
* toolchain/gcc: fix target-gcc for 4.3.xPeter Korsgaard2009-01-221-3/+8
| | | | | Includes are in include-fixed and GCC_LIB_SUBDIR needs to be set like for the rest of 4.x
* toolchain: introduce HOSTCC_VERSION and fix gcc-4.3.x build with old host CCsPeter Korsgaard2009-01-191-2/+9
| | | | | | | | gcc < 4.2.0 doesn't support -Wno-overlength-stings, but gcc-4.3.x configure fails to detect that, breaking the build. Work around it by detecting the host gcc version (and store in HOSTCC_VERSION) and set the proper configure variables for gcc < 4.2.0.
* Update broken AVR32 toolchain, and update configs for this, deprecate all ↵Ulf Samuelsson2009-01-161-0/+5
| | | | but latest AVR32 toolchain
* toolchain/: convert to DOWNLOAD helperPeter Korsgaard2009-01-161-1/+1
|
* toolhain/: confgure: respect quiet optionPeter Korsgaard2008-10-261-0/+1
|
* gcc: make installation of shared libraries multi-project safeHans-Christian Egtvedt2008-10-021-4/+5
| | | | | | | | | This patch modifies the rule for installing the shared libraries into the project_foo/.../autotools-stamps directory. This will make the installation of GCC shared libraries be multi-project safe. Signed-off-by: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
* gcc: make sure that /usr/lib exists on target before installing shared libsHans-Christian Egtvedt2008-10-021-0/+1
| | | | | | | | On very lite systems the /usr/lib directory might not exist before libstdc++ is installed. This patch makes sure the directory exists. Signed-off-by: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-09 03:26:26 +0000