From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: buildroot@buildroot.org, Fabio Estevam <festevam@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/1] configs/freescale_imx93frdm: bump U-Boot, TF-A and Linux
Date: Wed, 29 Jul 2026 18:04:39 +0200 [thread overview]
Message-ID: <b65e70c2fe7fd1be78cb0deebf3d5f87@free.fr> (raw)
In-Reply-To: <6a9c4d00-ef01-72a1-5e11-24341ffd8b1f@crashcourse.ca>
Hi Robert,
On 29/07/2026 12:05, Robert P. J. Day wrote:
> On Sun, 26 Jul 2026, Julien Olivain wrote:
>
>> Since Buildroot commit [1] "package/gcc: switch to GCC 15.x as the
>> default", compiling freescale_imx93frdm_defconfig fails in TF-A with
>> error:
>>
>> include/drivers/nxp/trdc/imx_trdc.h:7: error: header guard
>> 'IMX_TRDC_H' followed by '#define' of a different macro
>> [-Werror=header-guard]
>> 7 | #ifndef IMX_TRDC_H
>> include/drivers/nxp/trdc/imx_trdc.h:8: note: 'IMX_XRDC_H' is
>> defined here; did you mean 'IMX_TRDC_H'?
>> 8 | #define IMX_XRDC_H
>>
>> The issue happen because this defconfig is using a Buildroot
>> (internal) toolchain which uses gcc version 15 by default.
>>
>> This issue was fixed upstream in [2], first included in TF-A v2.13.
>>
>> This commit updates U-Boot, TF-A and Linux to use the NXP
>> tag lf-6.18.20-2.0.0, which include this fixes.
>>
>> Note that, as described in the commit log of [3] which introduced
>> this defconfig, U-Boot and Linux were forks. Now the necessary
>> patches are included in the vendor BSP, this commit switches those
>> repos to use the vendor ones.
>>
>> While at it, this commit also switches the defconfig to use an
>> external glibc stable Bootlin toolchain, to follow recommendations
>> from [4]. Since an external toolchain is used, the linux-headers.hash
>> custom hash file is no longer needed and is also removed. At the
>> time of this commit, the Bootlin stable toolchain is a gcc 14.
>>
>> Also, due to the upstream uboot commit [5], this commit adds a uboot
>> config fragment to disable CONFIG_EFI_CAPSULE_AUTHENTICATE, to
>> remove the dependency on the command "cert-to-efi-sig-list", provided
>> the host efitools package, which is not yet in Buildroot.
>>
>> This commit was run tested on board 700-94611 Rev B1.
>>
>> [1]
>> https://gitlab.com/buildroot.org/buildroot/-/commit/a75b8623f5515d99bec48f96586115953150558e
>> [2]
>> https://git.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a.git/+/2e9198d0e0cbe9546348dd0a71ff6c3d2061d4eb%5E%21/
>> [3]
>> https://gitlab.com/buildroot.org/buildroot/-/commit/2e05f22ff862192a7e512d0db0486351bba94ae8
>> [4]
>> https://elinux.org/Buildroot:DeveloperDaysELCE2024#Rules_for_defconfigs
>> [5]
>> https://git.u-boot-project.org/u-boot/u-boot/-/commit/fd58c275f6ba524101ba0990e53f5a11ac390bd0
>>
>> Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
>> Signed-off-by: Julien Olivain <ju.o@free.fr>
>> ---
>
> ... snip patch ...
>
> Is there an ETA on when this will be applied to master? Or am I
> supposed to fetch it from some other staging-type branch?
The patch is waiting for a reviewer and/or a tester.
Since you are the initial reporter of this issue, it would be great if
you could test this proposed patch on your side. Then reply with
comments or saying the issue is fixed (and how you tested), with a
"Tested-by: ..." tag.
Only then, a maintainer will merge the patch in master.
See:
https://nightly.buildroot.org/manual.html#_reviewing_and_testing_patches
> rday
Best regards,
Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-07-29 16:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-26 20:44 [Buildroot] [PATCH 1/1] configs/freescale_imx93frdm: bump U-Boot, TF-A and Linux Julien Olivain via buildroot
2026-07-29 10:05 ` Robert P. J. Day
2026-07-29 16:04 ` Julien Olivain via buildroot [this message]
2026-07-29 18:42 ` Robert P. J. Day
2026-07-29 18:57 ` Julien Olivain via buildroot
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=b65e70c2fe7fd1be78cb0deebf3d5f87@free.fr \
--to=buildroot@buildroot.org \
--cc=festevam@gmail.com \
--cc=ju.o@free.fr \
--cc=rpjday@crashcourse.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.