deepcrayon
/
buildroot
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

toolchain-external: clarify the comment about *-gcc-ar... LTO wrappers 

Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015.11.x
Arnout Vandecappelle 2015-09-12 01:24:20 +02:00 committed by Thomas Petazzoni
parent cdbaba0a2e
commit 797318b483
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
toolchain/toolchain-external/toolchain-external.mk
View File

@ -666,11 +666,12 @@ endif
# Build toolchain wrapper for preprocessor, C and C++ compiler and setup
# symlinks for everything else. Skip gdb symlink when we are building our
# own gdb to prevent two gdb's in output/host/usr/bin.
# When the link-time-optimization flag '-flto' is used, then the compiler
# and binutils have to support lto. ar/ranlib need to be called with the
# lto plugin. The wrappers *-gcc-ar and *-gcc-ranlib provided by GCC could
# be used as drop-ins for ar/runlib when Makefiles are used which do not
# pass the lto arguments.
# The LTO support in gcc creates wrappers for ar, ranlib and nm which load
# the lto plugin. These wrappers are called *-gcc-ar, *-gcc-ranlib, and
# *-gcc-nm and should be used instead of the real programs when -flto is
# used. However, we should not add the toolchain wrapper for them, and they
# match the *cc-* pattern. Therefore, an additional case is added for *-ar,
# *-ranlib and *-nm.
define TOOLCHAIN_EXTERNAL_INSTALL_WRAPPER
$(Q)$(call MESSAGE,"Building ext-toolchain wrapper")
$(Q)mkdir -p $(HOST_DIR)/usr/bin