Starting with kernel >= v5.7 the build system can override this
variable by passing LLVM=1 [1], but for older kernels or in
cases where the LLVM toolchain is setup directly via portage,
CC should be respected to avoid situations like building the
kernel with clang but the headers with gcc.
[1] a0d1c951ef08 kbuild: support LLVM=1 to switch the default tools to Clang/LLVM
Co-authored-by: Manoj Gupta <
manojgupta@chromium.org>
Signed-off-by: Adrian Ratiu <
adrian.ratiu@collabora.com>
---
eclass/kernel-2.eclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/eclass/kernel-2.eclass b/eclass/kernel-2.eclass
index adc1425bc2e..9a7d96d26c7 100644
--- a/eclass/kernel-2.eclass
+++ b/eclass/kernel-2.eclass
@@ -692,7 +692,7 @@ env_setup_xmakeopts() {
elif type -p ${CHOST}-ar >/dev/null; then
xmakeopts="${xmakeopts} CROSS_COMPILE=${CHOST}-"
fi
- xmakeopts="${xmakeopts} HOSTCC=$(tc-getBUILD_CC)"
+ xmakeopts="${xmakeopts} HOSTCC=$(tc-getBUILD_CC) CC=$(tc-getCC)"
export xmakeopts
}
--
2.34.0
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)