aboutsummaryrefslogtreecommitdiffstats
path: root/include/download.mk
diff options
context:
space:
mode:
authorFelix Fietkau <nbd@openwrt.org>2014-12-27 12:59:59 +0000
committerFelix Fietkau <nbd@openwrt.org>2014-12-27 12:59:59 +0000
commit9a467998042abfc0b1c7c5e4420c27615544cee3 (patch)
treee6b594bfb7ea241ff11e809b552c4058eab7083a /include/download.mk
parent7d808a325d47f1f5ae09db0eb8a99e6cfe5632c9 (diff)
downloadupstream-9a467998042abfc0b1c7c5e4420c27615544cee3.tar.gz
upstream-9a467998042abfc0b1c7c5e4420c27615544cee3.tar.bz2
upstream-9a467998042abfc0b1c7c5e4420c27615544cee3.zip
build: use gcc-provided ar, nm and ranlib where appropriate
Since GCC 4.7, GCC provides its own wrappers around ar, nm and ranlib, which should be used for builds with link-time optimization. Since GCC 4.9, using them actually necessary for LTO builds using convenience libraries to succeed. There are some packages which try to automatically detect if gcc-{ar,nm,ranlib} exist (one example is my package "fastd" in the package repository, which tries to use LTO). This breaks because the OpenWrt build system explicitly sets the binutils versions of these tools. As it doesn't cause any issues to use gcc-{ar,nm,ranlib} instead of {ar,nm,ranlib} even without LTO, this patch just makes OpenWrt use the GCC-provided versions by default, which fixes the build of such packages with GCC 4.9. (I know that builds fail though when clang is used with -flto and gcc-{ar,nm,ranlib}, but as all OpenWrt toolchains are based on GCC, this isn't a real issue.) Completely cleaning the tree (or at least `make clean toolchain/clean`) is necessary to get a consistent state after the binutils plugins support patch and this one (as trying to use gcc-{ar,nm,ranlib} with a binutils built without plugin support will definitely lead to a build failure). Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net> SVN-Revision: 43784
Diffstat (limited to 'include/download.mk')
0 files changed, 0 insertions, 0 deletions