From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org,
Giulio Benetti <giulio.benetti@benettiengineering.com>,
Romain Naour <romain.naour@gmail.com>
Subject: Re: [Buildroot] [PATCH] tooolchain/toolchain-external: update toolchain-external-bootlin to 2026.08
Date: Tue, 08 Sep 2026 21:03:19 +0200 [thread overview]
Message-ID: <c78c97e29a00c77fba83bb137ec8df47@free.fr> (raw)
In-Reply-To: <20260908125457.211667-1-thomas.petazzoni@bootlin.com>
On 08/09/2026 14:54, Thomas Petazzoni via buildroot wrote:
> All toolchains have been rebuilt based on Buildroot 2026.08, which
> means:
>
> * The bleeding-edge toolchains are based on gcc 16.2, binutils 2.46.1,
> gdb 17.1, kernel headers 6.12, glibc 2.44, musl 1.2.6 or uclibc-ng
> 1.0.59.
>
> * The stable toolchains are based on gcc 15.3, binutils 2.45.1, gdb
> 16.3, kernel headers 5.10, glibc 2.44, musl 1.2.6 or uclibc-ng
> 1.0.59.
>
> The runtime tests related to those toolchains all pass fine:
>
> https://gitlab.com/tpetazzoni/buildroot/-/pipelines/2824569690
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-09-08 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 12:54 [Buildroot] [PATCH] tooolchain/toolchain-external: update toolchain-external-bootlin to 2026.08 Thomas Petazzoni via buildroot
2026-09-08 19:03 ` Julien Olivain via buildroot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-09-06 18:07 Thomas Petazzoni 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=c78c97e29a00c77fba83bb137ec8df47@free.fr \
--to=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=ju.o@free.fr \
--cc=romain.naour@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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