all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Janneke Nieuwenhuizen <janneke@gnu.org>
Cc: ekaitz@elenq.tech, andreas@enge.fr, efraim@flashner.co.il,
	74676@debbugs.gnu.org
Subject: [bug#74676] [core-packages-team 5/5] DRAFT gnu: gcc: Update gcc, gcc-toolchain to 14.
Date: Thu, 26 Dec 2024 12:07:46 +0100	[thread overview]
Message-ID: <87ldw2ya65.fsf@gnu.org> (raw)
In-Reply-To: <8734in717q.fsf@gnu.org> (Janneke Nieuwenhuizen's message of "Mon, 16 Dec 2024 22:43:53 +0100")

Hi,

Janneke Nieuwenhuizen <janneke@gnu.org> skribis:

> I've built the rust bootstrap several times already, guess I'll just go
> for a new round.  But this time we can maybeu "cheat" with packages that
> are too difficult to build, and build them with another gcc version than
> 14?

I haven’t followed closely (sorry!), but if it’s just a matter of adding
‘gcc-11’ (say) as a native input for a couple of packages, that’s
probably okay.  Except perhaps for C libraries, because then we could
end up with programs depending on two difference versions of libgcc_s.so
& co.

Ludo’.




  reply	other threads:[~2024-12-26 11:08 UTC|newest]

Thread overview: 7+ 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
2024-12-16 21:43     ` Janneke Nieuwenhuizen
2024-12-26 11:07       ` Ludovic Courtès [this message]
2025-01-06 13:30         ` Janneke Nieuwenhuizen
2024-12-29 15:05 ` Ludovic Courtès

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=87ldw2ya65.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=74676@debbugs.gnu.org \
    --cc=andreas@enge.fr \
    --cc=efraim@flashner.co.il \
    --cc=ekaitz@elenq.tech \
    --cc=janneke@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.