diff options
| author | Arnd Bergmann <arnd@arndb.de> | 2025-02-25 11:00:31 +0100 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2025-06-27 11:07:25 +0100 |
| commit | df3670a8be5174b0243e1879ad8f114b6a3df9e3 (patch) | |
| tree | 31df166b0a9ea6770ce1e44411b6e96ec873aebc /usr | |
| parent | 64ccf310c5f9f0ab504317aa9e032f804572dda5 (diff) | |
| download | linux-df3670a8be5174b0243e1879ad8f114b6a3df9e3.tar.gz linux-df3670a8be5174b0243e1879ad8f114b6a3df9e3.tar.bz2 linux-df3670a8be5174b0243e1879ad8f114b6a3df9e3.zip | |
kbuild: hdrcheck: fix cross build with clang
commit 02e9a22ceef0227175e391902d8760425fa072c6 upstream.
The headercheck tries to call clang with a mix of compiler arguments
that don't include the target architecture. When building e.g. x86
headers on arm64, this produces a warning like
clang: warning: unknown platform, assuming -mfloat-abi=soft
Add in the KBUILD_CPPFLAGS, which contain the target, in order to make it
build properly.
See also 1b71c2fb04e7 ("kbuild: userprogs: fix bitsize and target
detection on clang").
Reviewed-by: Nathan Chancellor <nathan@kernel.org>
Fixes: feb843a469fb ("kbuild: add $(CLANG_FLAGS) to KBUILD_CPPFLAGS")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'usr')
| -rw-r--r-- | usr/include/Makefile | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/usr/include/Makefile b/usr/include/Makefile index 07796df0a295..c16fbabb3625 100644 --- a/usr/include/Makefile +++ b/usr/include/Makefile @@ -10,7 +10,7 @@ UAPI_CFLAGS := -std=c90 -Wall -Werror=implicit-function-declaration # In theory, we do not care -m32 or -m64 for header compile tests. # It is here just because CONFIG_CC_CAN_LINK is tested with -m32 or -m64. -UAPI_CFLAGS += $(filter -m32 -m64 --target=%, $(KBUILD_CFLAGS)) +UAPI_CFLAGS += $(filter -m32 -m64 --target=%, $(KBUILD_CPPFLAGS) $(KBUILD_CFLAGS)) # USERCFLAGS might contain sysroot location for CC. UAPI_CFLAGS += $(USERCFLAGS) |