From a0249703fd628fc0a74f6a7505b2be8acd9084ca Mon Sep 17 00:00:00 2001 From: Alexey Neyman Date: Tue, 19 Feb 2019 17:38:21 -0800 Subject: [PATCH] Duh! do not override ${cflags} ... in the backend function with ${CFLAGS_FOR_HOST}. The caller either supplies them already, or (in case of pass-1/2 of the canadian cross) passes ${CFLAGS_FOR_BUILD} there. Signed-off-by: Alexey Neyman --- scripts/build/cc/gcc.sh | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/scripts/build/cc/gcc.sh b/scripts/build/cc/gcc.sh index 9ba5982f..ce7fea4c 100644 --- a/scripts/build/cc/gcc.sh +++ b/scripts/build/cc/gcc.sh @@ -542,9 +542,10 @@ do_gcc_core_backend() { CT_DoLog DEBUG "Extra config passed: '${extra_config[*]}'" - # We may need to modify host/build CFLAGS separately below + # We may need to modify host/build/target CFLAGS separately below. Note + # that ${cflags} may refer either to build or host CFLAGS; they are provided + # by the caller. cflags_for_build="${CT_CFLAGS_FOR_BUILD}" - cflags="${CT_CFLAGS_FOR_HOST}" cflags_for_target="${CT_TARGET_CFLAGS}" # Clang's default bracket-depth is 256, and building GCC