From: Quentin Schulz <quentin.schulz@cherry.de>
To: Ross Burton <Ross.Burton@arm.com>
Cc: "Harish.Sadineni@windriver.com" <Harish.Sadineni@windriver.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
"Sundeep.Kokkonda@windriver.com" <Sundeep.Kokkonda@windriver.com>
Subject: Re: [OE-core] [PATCH] u-boot: add support for Clang toolchain
Date: Tue, 11 Aug 2026 14:32:24 +0200 [thread overview]
Message-ID: <5c5b2aa3-08ba-4491-8f1d-75216be08252@cherry.de> (raw)
In-Reply-To: <58AB193A-9DA4-4BC4-BC53-94FDA2D986D4@arm.com>
Hi Ross,
On 8/11/26 2:21 PM, Ross Burton wrote:
> On 11 Aug 2026, at 13:13, Quentin Schulz <quentin.schulz@cherry.de> wrote:
>> Why not simply ${TOOLCHAIN}?
>
> That would be a big assumption that TOOLCHAIN is also the name of the binary, which fails for any native builds.
>
> But it would also work here…
>
OK. Let's rather not use anti-patterns whenever we can so people aren't
tempted to copy this for recipes that can be native/nativesdk too.
Please ignore my suggestion for TOOLCHAIN.
>> Have you checked we can build u-boot-tools, u-boot-tools-native and nativesdk-u-boot-tools with clang?
>
> FWIW, upstream CI exercises the build with clang so it should work. Our CI will be doing build+boot tests of some clang builds with qemu.
>
From my shell history when I built Rockchip boards in U-Boot with clang
a few months ago I had run:
make CROSS_COMPILE="aarch64-linux-gnu-" O=build/puma HOSTCC=clang
CC=clang puma-rk3399_defconfig
So we need to check HOSTCC is proper and that we really need to add
${TARGET_PREFIX} in front of gcc/clang in CC.
I thought u-boot-tools includes u-boot.inc but it doesn't, so ignore my
previous comment (we should however verify at some point we can build
with either toolchain).
Cheers,
Quentin
prev parent reply other threads:[~2026-08-11 12:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 10:56 [PATCH] u-boot: add support for Clang toolchain Harish.Sadineni
2026-08-11 12:13 ` [OE-core] " Quentin Schulz
2026-08-11 12:21 ` Ross Burton
2026-08-11 12:32 ` Quentin Schulz [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=5c5b2aa3-08ba-4491-8f1d-75216be08252@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=Harish.Sadineni@windriver.com \
--cc=Ross.Burton@arm.com \
--cc=Sundeep.Kokkonda@windriver.com \
--cc=openembedded-core@lists.openembedded.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