Re: [OE-core] [PATCH] u-boot: always use GCC to build

[Quentin Schulz <quentin.schulz@cherry.de>]

Hi Ross,

On 8/4/26 1:41 PM, Ross Burton via lists.openembedded.org wrote:
> Previously, u-boot was almost always built with GCC because the
> kernel-arch inherit set TOOLCHAIN to KERNEL_TOOLCHAIN, which defaulted
> to 'gcc'.
> 
> However, since kernel-arch inherit was removed, u-boot in theory now
> respects the default toolchain. In practise, the recipe hard-codes CC
> to be gcc, and there are known caveats building u-boot with clang[2].
> 
> In the long term we should be able to make this recipe respect TOOLCHAIN,
> as the upstream u-boot CI does build and test with clang, but for now
> fix the build by restoring the explicit use of gcc.
> 

You don't say what is the issue we encounter when building this recipe 
with clang so this can be summed up to "fix issue" which isn't 
particularly helpful :) Could you consider providing a bit more info 
about build breakage in the commit log? I've built semi-recently (a few 
months ago) Rockchip (ARM and ARM64) devices with clang and couldn't 
build any of the ARM (thus 32b) SoCs at that time. I am traveling right 
now so cannot give you a link to the U-Boot ML archive but look for 
"Couple of clang warnings for Rockchip boards" from April 22nd, 2026.

Cheers,
Quentin