From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Toolchain Update to GCC 12.2.0 and binutils 2.40
Date: Mon, 30 Jan 2023 12:15:14 +0000 [thread overview]
Message-ID: <20230130121520.4038402-1-michael.tremer@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 457 bytes --]
Hello everyone,
this is a patchset that updates the toolchain for IPFire 2.
It has been a smooth ride with only three packages needing some extra
attention to build this all. So I would say this is safe to be merged.
The pre-compiled toolchains have been built and uploaded by me, so this
is good to go.
However, I do not think that this shoud be a part of Core Update 173 as
that is already quite large with a new kernel and so on...
Best,
-Michael
next reply other threads:[~2023-01-30 12:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 12:15 Michael Tremer [this message]
2023-01-30 12:15 ` [PATCH 1/6] binutils: Update to 2.40 Michael Tremer
2023-01-30 12:15 ` [PATCH 3/6] ccache: Use the correct header files from the toolchain Michael Tremer
2023-01-30 12:15 ` [PATCH 4/6] boost: Update to 1.81.0 Michael Tremer
2023-01-30 12:15 ` [PATCH 5/6] mpd: Update to 0.23.12 Michael Tremer
2023-01-30 12:15 ` [PATCH 6/6] make.sh: Bump toolchain version Michael Tremer
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=20230130121520.4038402-1-michael.tremer@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/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