unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Rutherther via Guix-patches via <guix-patches@gnu.org>
To: 73793@debbugs.gnu.org
Cc: Rutherther <rutherther@ditigal.xyz>,
	Rutherther <rutherther@ditigal.xyz>,
	"Andreas Enge" <andreas@enge.fr>,
	"Ludovic Courtès" <ludo@gnu.org>
Subject: [bug#73793] [PATCH v2 0/1] Fixes of the patch for gcc 9
Date: Sun, 13 Oct 2024 19:10:56 +0200	[thread overview]
Message-ID: <cover.1728836876.git.rutherther@ditigal.xyz> (raw)
In-Reply-To: <f18d0454c198003e64c962d3e3b4de5ab9c930b4.1728832424.git.rutherther@ditigal.xyz>

I forgot to change the name guix has in the source from
the one llvm has. Additionally, I also managed to put the
patch to gcc-10 instead of gcc-9. So fixed that as well

The gcc now builds fine for me on x86_64-linux.

Regards,
Rutherther

Rutherther (1):
  gnu: gcc-9: Fix name conflict for newer glibc versions

 gnu/local.mk                                  |  1 +
 gnu/packages/gcc.scm                          |  3 +-
 .../patches/gcc-9-glibc-name-conflict.patch   | 54 +++++++++++++++++++
 3 files changed, 57 insertions(+), 1 deletion(-)
 create mode 100644 gnu/packages/patches/gcc-9-glibc-name-conflict.patch


base-commit: 8f0d76152a4496960f4c2ec219839c5a48b0568e
--
2.46.0




  reply	other threads:[~2024-10-13 17:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-13 15:22 [bug#73793] [PATCH] gnu: gcc-9: Fix name conflict for newer glibc versions Rutherther via Guix-patches via
2024-10-13 17:10 ` Rutherther via Guix-patches via [this message]
2024-10-13 17:10 ` [bug#73793] [PATCH v2] " Rutherther via Guix-patches via
2024-10-14 11:52 ` [bug#73793] [PATCH] " Ludovic Courtès
2024-10-14 18:00 ` [bug#73793] [PATCH v3] gnu: gcc-9: Add libsanitizer fsconfig command patch Rutherther via Guix-patches via
2024-10-15 15:45   ` bug#73793: " 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

  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=cover.1728836876.git.rutherther@ditigal.xyz \
    --to=guix-patches@gnu.org \
    --cc=73793@debbugs.gnu.org \
    --cc=andreas@enge.fr \
    --cc=ludo@gnu.org \
    --cc=rutherther@ditigal.xyz \
    /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).