more/freebsd-11-stable/Makefile.inc1

54 # Cross toolchain changes must be in effect before bsd.compiler.mk
72 # If a full path to an external cross compiler is given, don't build
73 # a cross compiler.
86 # Pull in compiler metadata from buildworld/toolchain if possible to avoid
87 # running CC from bsd.compiler.mk.
90 .-include "${OBJTREE}${.CURDIR}/compiler-metadata.mk"
97 .include <bsd.compiler.mk>
100 # Check if there is a local compiler that can satisfy as an external compiler.
101 # Which compiler is expected to be used?
142 # Everything matches, disable the bootstrap compiler.
156 test-system-compiler: .PHONY
163 .info SYSTEM_COMPILER: Determined that CC=${CC} matches the source tree.  Not bootstrapping a cross-compiler.
166 # For installworld need to ensure that the looked-up compiler metadata is
182 # Store some compiler metadata for use in installworld where we don't
191 compiler-metadata.mk: .PHONY .META
193 	@echo ".info Using cached compiler metadata from build at $$(hostname) on $$(date)" \
475 #	are needed for building the system. A cross-compiler is one
579 # directory, but the compiler will look in the right place for its
584 # External compiler needs sysroot and target flags.
597 # GCC requires -isystem and -L when using a cross-compiler.  --sysroot
794 	@rm -f ${OBJTREE}${.CURDIR}/compiler-metadata.mk
800 	@echo ">>> stage 3.1: recording compiler metadata"
802 	${_+_}cd ${.CURDIR}; ${WMAKE} compiler-metadata.mk
1717 # binaries is usually quite narrow. Bootstrap tools use the host's compiler and
2670 # GCC requires -isystem and -L when using a cross-compiler.  --sysroot
2674 # GCC requires -B to find /usr/lib/crti.o when using a cross-compiler