From: "Ludovic Courtès" <ludo@gnu.org>
To: Janneke Nieuwenhuizen <janneke@gnu.org>
Cc: 74676@debbugs.gnu.org, Andreas Enge <andreas@enge.fr>,
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, 29 Dec 2024 16:05:34 +0100 [thread overview]
Message-ID: <8734i6r0ld.fsf@gnu.org> (raw)
In-Reply-To: <87ed2ofpbo.fsf@gnu.org> (Janneke Nieuwenhuizen's message of "Tue, 03 Dec 2024 22:07:23 +0100")
Hello,
Janneke Nieuwenhuizen <janneke@gnu.org> skribis:
> Before pointing the build farm to core-packages-team and starting the
> "real work" we may want to think about how to go forward. On the one
> hand, having CFLAGS patches littered all over the place is not great, on
> the other hand, if we were to add compatibility flags to a wrapper for
> gcc, or into build systems, we may never get rid of such a "feature".
> Thoughts?
The -Wno-implicit-function-declaration CFLAGS/patches all around are not
pretty, but they’ll vanish over time.
A wrapper would be problematic for the reason you give notably. (In the
early days of Guix, I tried really hard to avoid compiler wrappers,
which is what Nixpkgs has, to remain as close as possible to the
toolchain and to avoid “invisible magic” afforded by wrappers.)
Ludo’.
prev parent reply other threads:[~2024-12-29 15:06 UTC|newest]
Thread overview: 6+ 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
2024-12-29 15:05 ` Ludovic Courtès [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=8734i6r0ld.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 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).