From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2023.07.0 released
Date: Wed, 5 Jul 2023 16:27:31 +0200 [thread overview]
Message-ID: <ZKV90zkjJMAJj1Fm@pengutronix.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1478 bytes --]
Hi,
I'm happy to announce that I've just released OSELAS.Toolchain-2023.07.0.
This is a major release with significant changes. All components of the
primary toolchains have been updated to the latest versions. The highlights
are:
- binutils 2.40
- clang 16.0.6
- gcc 13.1
- gdb 13.2
- glibc 2.37
- kernel headers 6.3.6
- rustc 1.70.0
Beyond that, the most significant change is, that hacks to install
everything in /lib even on 64-bit architectures are gone. So the dynamic
linker and libraries may now be found in /lib64 etc.
PTXdist was updated to handle this, so at least ptxdist-2023.07.0 will be
needed to build BSPs with 64-bit toolchains.
The uclibc toolchains have been removed.
There is a new toolchain for loongarch64-linux-gnu.
Download the release here:
https://public.pengutronix.de/oselas/toolchain/
Debian / Ubuntu Packages will be available at
http://debian.pengutronix.de/
My current plan is to build packages for Debian trixie/sid, bookworm,
bullseye and Ubuntu 20.04, 22.04. I may build packages for Debian
buster and Ubuntu 18.04 but that depends on how easy that is.
Enjoy,
Michael Olbrich
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2023-07-05 14:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ZKV90zkjJMAJj1Fm@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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