From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Romain Naour <romain.naour@gmail.com>,
Giulio Benetti <giulio.benetti@benettiengineering.com>,
Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] toolchain/toolchain-external/toolchain-external-bootlin: update to 2023.11-1
Date: Thu, 28 Dec 2023 22:05:59 +0100 [thread overview]
Message-ID: <ZY3jN2pXiI6ZEb-A@landeda> (raw)
In-Reply-To: <20231227171343.2903354-2-thomas.petazzoni@bootlin.com>
Thomas, All,
On 2023-12-27 18:13 +0100, Thomas Petazzoni via buildroot spake thusly:
> New toolchains have been released, with the following changes:
>
> - The bleeding-edge toolchains are based on gcc 13.2, binutils 2.41,
> gdb 14.1, kernel headers 5.10, glibc 2.38, musl 1.2.4 or uclibc-ng
> 1.0.45.
>
> - The stable toolchains are based on gcc 12.3, binutils 2.40, gdb
> 13.2, kernel headers 4.14, glibc 2.38, musl 1.2.4 or uclibc-ng
> 1.0.45.
>
> - The glibc version is no longer affected by CVE-2023-4911
>
> - The gdb build has been fixed to no longer rely on uninstalled
> libbfd.so and libopcodes.so libraries
>
> - The zlib library, which was incorrectly present in the toolchain
> sysroot, is gone, fixing various build failures encountered with
> 2023.08 toolchains.
>
> - There are now toolchains for m68k 68xxx based on uclibc and musl in
> addition to glibc, which was already supported
>
> The careful reviewer will notice that a number of
>
> depends on !BR2_ARCH_NEEDS_GCC_AT_LEAST_14
>
> are being added to the toolchains that use gcc 13.x, as per
> a0d2a5cfec0ade7cb577cbff25aac289e746e61b
> ("support/scripts/gen-bootlin-toolchains: generate
> BR2_ARCH_NEEDS_GCC_AT_LEAST_X guard").
>
> All 214 test cases were successfully run:
>
> https://gitlab.com/tpetazzoni/buildroot/-/pipelines/1120323562
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Applied to master, thanks.
Regards,
Yann E. MORIN.
[--SNIP big patch--]
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-12-28 21:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 17:13 [Buildroot] [PATCH 1/2] arch/Config.in: introduce BR2_ARCH_NEEDS_GCC_AT_LEAST_14 Thomas Petazzoni via buildroot
2023-12-27 17:13 ` [Buildroot] [PATCH 2/2] toolchain/toolchain-external/toolchain-external-bootlin: update to 2023.11-1 Thomas Petazzoni via buildroot
2023-12-28 21:05 ` Yann E. MORIN [this message]
2023-12-28 21:04 ` [Buildroot] [PATCH 1/2] arch/Config.in: introduce BR2_ARCH_NEEDS_GCC_AT_LEAST_14 Yann E. MORIN
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=ZY3jN2pXiI6ZEb-A@landeda \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=romain.naour@gmail.com \
--cc=thomas.de_schampheleire@nokia.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