summaryrefslogtreecommitdiff
path: root/package/binutils/binutils.mk
AgeCommit message (Collapse)Author
2012-05-19binutils: fix build with external toolchains on avr32Peter Korsgaard
Fixes http://autobuild.buildroot.org/results/7f0545a7c824bf0523ab3506db83f7f5c930d63d/ Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-04-25toolchain: remove useless indirect variablesThomas Petazzoni
The BR2_CONFIGURE_DEVEL_SYSROOT, BR2_CONFIGURE_STAGING_SYSROOT and BR2_CONFIGURE_BUILD_TOOLS were used only in a few places, and it is in fact clearer to just use their value in the various places they are used. The ultimate goal is to get rid of the toolchain/Makefile.in file. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-01-18binutils: unbreak host build after auto-host-deps changePeter Korsgaard
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-10-27binutils: Makefile and Config.in rework for oprofile ext toolchain compilationBenoit Mauduit
* When select full binutils binaries use the default INSTALL_TARGET_CMDS from AUTOTARGET. * Menu config improvement. * Install libiberty into Staging dir. [Peter: Fix typos, Config.in fixes, install libiberty to target as well] Signed-off-by: Benoit Mauduit <benoit.mauduit@openwide.fr> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-10-02binutils: build host version staticallyPeter Korsgaard
Otherwise we end up with libbfd/libopcodes in host/usr/$BUILD/$TARGET/lib, used by the binaries. Unfortunately it also adds rpaths, which first look in the build directory before here, causing trouble if the toolchain is used outside BR (E.G. for a SDK) and the build directory location reused for another incompatible build (E.G. another ARCH), as the binutils binaries then end up using the wrong libs. Fix it by linking statically instead. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-09-29package: remove useless arguments from AUTOTARGETSThomas Petazzoni
Thanks to the pkgparentdir and pkgname functions, we can rewrite the AUTOTARGETS macro in a way that avoids the need for each package to repeat its name and the directory in which it is present. [Peter: pkgdir->pkgparentdir] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-01-02binutils: make it a proper packageGustavo Zacarias
* Convert binutils to a proper autotargets package * Add version 2.21 and drop version 2.17 * Hook up packaged binutils for target gcc * Build tools are on HOST_DIR now so change it * Move cross/host gcc to HOST_DIR * Drop kludge from commit 3c77bab2eeace3ee675bd745ca335fa3dd1630bb This is fixed in the next commit "gcc: install copies of libgcc, libstdc++ and libgcj to the sysroot" - tested for arm & x86_64 targets. * TARGET_CROSS now pointed to HOST_DIR too [Peter: Config.in tweaks] Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>