From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH 1/4] sandbox: make CC_HAS_LINUX_I386_SUPPORT depend on GCC
Date: Mon, 17 Feb 2025 11:46:08 +0100 [thread overview]
Message-ID: <20250217104611.1836442-1-a.fatoum@pengutronix.de> (raw)
CC_HAS_LINUX_I386_SUPPORT enables build for 32-bit with a 64-bit GCC
toolchain. This seems not to work correctly on clang:
CC arch/sandbox/os/common.o
In file included from arch/sandbox/os/common.c:23:
In file included from /usr/lib/llvm-16/lib/clang/16/include/limits.h:21:
/usr/include/limits.h:26:10: fatal error:
'bits/libc-header-start.h' file not found
#include <bits/libc-header-start.h>
So disable it for now.
Fixes: f41c4d7c5649 ("Makefile: add LLVM/clang support")
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
arch/sandbox/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/sandbox/Kconfig b/arch/sandbox/Kconfig
index 0b6cc75098be..c1a51d4f021d 100644
--- a/arch/sandbox/Kconfig
+++ b/arch/sandbox/Kconfig
@@ -40,6 +40,7 @@ config CC_IS_64BIT
config CC_HAS_LINUX_I386_SUPPORT
def_bool $(cc-option,-m32) && $(ld-option,-m elf_i386)
+ depends on CC_IS_GCC
config 64BIT
bool
--
2.39.5
next reply other threads:[~2025-02-17 10:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 10:46 Ahmad Fatoum [this message]
2025-02-17 10:46 ` [PATCH 2/4] Makefile: clang: fix typo in -Wno-typdef-redefinition flag Ahmad Fatoum
2025-02-17 10:46 ` [PATCH 3/4] kbuild: actually include Makefile.clang for clang builds Ahmad Fatoum
2025-02-17 10:46 ` [PATCH 4/4] Makefile: clang: fail non-sandbox LLVM builds early Ahmad Fatoum
2025-02-17 11:19 ` [PATCH 1/4] sandbox: make CC_HAS_LINUX_I386_SUPPORT depend on GCC Sascha Hauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250217104611.1836442-1-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox