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: Sun, 08 Dec 2024 19:13:08 +0100 [thread overview]
Message-ID: <87ldwqavrf.fsf@gnu.org> (raw)
In-Reply-To: <87ttbh52xh.fsf@gnu.org> (Janneke Nieuwenhuizen's message of "Thu, 05 Dec 2024 20:45:46 +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
That was apparently not true, somewhere in the process I somehow built from
another branch. Anyway, still making good progress.... :-/
On IRC, Efraim reports that i686-linux and aarch64-linux fail to build
hello on current core-packages-team. That makes me reconsider whether
this strategy
> I kept the scope narrow: x86_64-linux, because it has proven to be
> very hard to predict what's needed on other architectures.
which makes a lot of sense for patches that go to "master" is a good
strategy for core-packages-team. Possibly it's better to use an
unlimited scope? Oh well.
Greetings,
Janneke -- building /gnu/store/m5m6qzlxypk1y58yp69501rhq5qmz3r4-llvm-18.1.8.drv...
--
Janneke Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond https://LilyPond.org
Freelance IT https://www.JoyOfSource.com | Avatar® https://AvatarAcademy.com
prev parent reply other threads:[~2024-12-08 18:14 UTC|newest]
Thread overview: 3+ 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
2024-12-08 18:13 ` Janneke Nieuwenhuizen [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ldwqavrf.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).