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