From: Janneke Nieuwenhuizen <janneke@gnu.org>
To: 74676@debbugs.gnu.org
Cc: "Andreas Enge" <andreas@enge.fr>,
"Ludovic Courtès" <ludo@gnu.org>,
"Efraim Flashner" <efraim@flashner.co.il>,
"Ekaitz Zarraga" <ekaitz@elenq.tech>
Subject: [bug#74676] [core-packages-team 5/5] DRAFT gnu: gcc: Update gcc, gcc-toolchain to 14.
Date: Thu, 05 Dec 2024 20:45:46 +0100 [thread overview]
Message-ID: <87ttbh52xh.fsf@gnu.org> (raw)
In-Reply-To: <87ed2ofpbo.fsf@gnu.org> (Janneke Nieuwenhuizen's message of "Tue, 03 Dec 2024 22:07:23 +0100")
Janneke Nieuwenhuizen writes:
Hi,
> So, I've just built "hello" for x86_64-linux on "core-packages-team"
> (yay!) mostly re-using gcc-14 patches/workarounds that I created for the
> Hurd.
[..]
I've all but reconfigured--guix system reconfigure as non-root--my
system, without childhurd, using what is now core-packages-team-old.
That really wasn't so bad, many packages just build with gcc-14.
I have tried to keep the scope of changes as small as possible but
attempted to "fix" packages build failures also by upgrading the
package. For commencement and base packages I kept the scope narrow:
x86_64-linux, because it has proven to be very hard to predict what's
needed on other architectures. For other packages, such as "zip", I
just added the mostly harmless -Wno-implicit-function-declaration flag
unguarded.
The *-old branch has a couple of hacks that neutralize impact to
commencement packages, marked "REMOVEME", to avoid world rebuilds as
sometimes some base package builds in commencement, but fails to build
lateron.
The new, cleaned-up, and rebased core-packages-team branch is as such
untested, but "should work". WDYT? Can we point the build-farm to this
branch to help out?
Greetings,
Janneke
--
Janneke Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond https://LilyPond.org
Freelance IT https://www.JoyOfSource.com | Avatar® https://AvatarAcademy.com
next prev parent reply other threads:[~2024-12-05 19:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 21:07 [bug#74676] [core-packages-team 5/5] DRAFT gnu: gcc: Update gcc, gcc-toolchain to 14 Janneke Nieuwenhuizen
2024-12-05 19:45 ` Janneke Nieuwenhuizen [this message]
2024-12-08 18:13 ` Janneke Nieuwenhuizen
2024-12-16 21:43 ` Janneke Nieuwenhuizen
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=87ttbh52xh.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=74676@debbugs.gnu.org \
--cc=andreas@enge.fr \
--cc=efraim@flashner.co.il \
--cc=ekaitz@elenq.tech \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.