From: "Vincent Stehlé" <vincent.stehle@arm.com>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org, Dick Olsson <hi@senzilla.io>
Subject: Re: [Buildroot] [PATCH next 1/3] configs/aarch64_efi: switch to external toolchain
Date: Thu, 12 Mar 2026 16:49:49 +0100 [thread overview]
Message-ID: <abLgnUw4NQAuAgAx@debian> (raw)
In-Reply-To: <20260227215711.1232099-1-ju.o@free.fr>
On Fri, Feb 27, 2026 at 10:57:09PM +0100, Julien Olivain via buildroot wrote:
Hi Julien,
Thanks for refreshing aarch64-efi.
I verified that this patch series does indeed work fine on Compulab
IOT-GATE-iMX8 (eMMC), ROCKPro64 (SD card), Qemu virt, Qemu SBSA and FVP Base
RevC.
Feel free to add (or not):
Tested-by: Vincent Stehlé <vincent.stehle@arm.com>
Best regards,
Vincent.
> This commit switches the aarch64_efi_defconfig to an external glibc
> stable Bootlin toolchain, to follow recommendation from [1].
>
> Since an external toolchain is used, the linux-headers.hash custom
> hash file is no longer needed and is removed.
>
> [1] https://elinux.org/Buildroot:DeveloperDaysELCE2024#Rules_for_defconfigs
>
> Signed-off-by: Julien Olivain <ju.o@free.fr>
> ---
> board/aarch64-efi/patches/linux-headers/linux-headers.hash | 1 -
> configs/aarch64_efi_defconfig | 4 +++-
> 2 files changed, 3 insertions(+), 2 deletions(-)
> delete mode 120000 board/aarch64-efi/patches/linux-headers/linux-headers.hash
>
> diff --git a/board/aarch64-efi/patches/linux-headers/linux-headers.hash b/board/aarch64-efi/patches/linux-headers/linux-headers.hash
> deleted file mode 120000
> index 5808d92afe..0000000000
> --- a/board/aarch64-efi/patches/linux-headers/linux-headers.hash
> +++ /dev/null
> @@ -1 +0,0 @@
> -../linux/linux.hash
> \ No newline at end of file
> diff --git a/configs/aarch64_efi_defconfig b/configs/aarch64_efi_defconfig
> index 3aa649cf9c..2bc6740eaf 100644
> --- a/configs/aarch64_efi_defconfig
> +++ b/configs/aarch64_efi_defconfig
> @@ -1,5 +1,7 @@
> BR2_aarch64=y
> -BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_6_11=y
> +BR2_TOOLCHAIN_EXTERNAL=y
> +BR2_TOOLCHAIN_EXTERNAL_BOOTLIN=y
> +BR2_TOOLCHAIN_EXTERNAL_BOOTLIN_AARCH64_GLIBC_STABLE=y
> BR2_GLOBAL_PATCH_DIR="board/aarch64-efi/patches"
> BR2_DOWNLOAD_FORCE_CHECK_HASHES=y
> BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV=y
> --
> 2.53.0
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-03-12 15:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 21:57 [Buildroot] [PATCH next 1/3] configs/aarch64_efi: switch to external toolchain Julien Olivain via buildroot
2026-02-27 21:57 ` [Buildroot] [PATCH next 2/3] configs/aarch64_efi: bump kernel to 6.18.13 Julien Olivain via buildroot
2026-02-27 21:57 ` [Buildroot] [PATCH next 3/3] board/aarch64-efi/genimage-efi.cfg: use readable partition type Julien Olivain via buildroot
2026-03-12 15:49 ` Vincent Stehlé [this message]
2026-03-12 18:41 ` [Buildroot] [PATCH next 1/3] configs/aarch64_efi: switch to external toolchain Julien Olivain via buildroot
2026-03-20 15:55 ` Thomas Perale 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=abLgnUw4NQAuAgAx@debian \
--to=vincent.stehle@arm.com \
--cc=buildroot@buildroot.org \
--cc=hi@senzilla.io \
--cc=ju.o@free.fr \
/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.