From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH 1/4] sandbox: make CC_HAS_LINUX_I386_SUPPORT depend on GCC
Date: Mon, 17 Feb 2025 12:19:10 +0100 [thread overview]
Message-ID: <173979115074.1960646.7559186033947300422.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20250217104611.1836442-1-a.fatoum@pengutronix.de>
On Mon, 17 Feb 2025 11:46:08 +0100, Ahmad Fatoum wrote:
> 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>
>
> [...]
Applied, thanks!
[1/4] sandbox: make CC_HAS_LINUX_I386_SUPPORT depend on GCC
https://git.pengutronix.de/cgit/barebox/commit/?id=15af5003ba06 (link may not be stable)
[2/4] Makefile: clang: fix typo in -Wno-typdef-redefinition flag
https://git.pengutronix.de/cgit/barebox/commit/?id=35309a815da3 (link may not be stable)
[3/4] kbuild: actually include Makefile.clang for clang builds
https://git.pengutronix.de/cgit/barebox/commit/?id=c5370032370a (link may not be stable)
[4/4] Makefile: clang: fail non-sandbox LLVM builds early
https://git.pengutronix.de/cgit/barebox/commit/?id=aaea175ad00f (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2025-02-17 11:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 10:46 Ahmad Fatoum
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 ` Sascha Hauer [this message]
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=173979115074.1960646.7559186033947300422.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=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