From: "Ludovic Courtès" <ludo@gnu.org>
To: Rutherther <rutherther@ditigal.xyz>
Cc: 73793-done@debbugs.gnu.org
Subject: bug#73793: [PATCH v3] gnu: gcc-9: Add libsanitizer fsconfig command patch
Date: Tue, 15 Oct 2024 17:45:46 +0200 [thread overview]
Message-ID: <87sesxwes5.fsf@gnu.org> (raw)
In-Reply-To: <a0ab94712628f3dc38a4e65ec9d39a0166c158b2.1728928341.git.rutherther@ditigal.xyz> (rutherther@ditigal.xyz's message of "Mon, 14 Oct 2024 20:00:28 +0200")
Rutherther <rutherther@ditigal.xyz> skribis:
> Since newer glibc version there is a conflict in names
> between kernel module and glibc module.
> This uses a patch that was used upstream in llvm to bypass it.
> Without this, the build fails with a redefinition error.
>
> * gnu/packages/gcc.scm: Add gcc-7-libsanitizer-fsconfig-command.patch.
>
> Change-Id: Ibb8446b7bba52f72d82fcf69804cae09215daeed
I tweaked the commit log to clarify which entities are changed.
Applied, thanks!
Ludo’.
prev parent reply other threads:[~2024-10-15 15:58 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 ` [bug#73793] [PATCH v2 0/1] Fixes of the patch for gcc 9 Rutherther via Guix-patches via
2024-10-13 17:10 ` [bug#73793] [PATCH v2] gnu: gcc-9: Fix name conflict for newer glibc versions 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 ` 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=87sesxwes5.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=73793-done@debbugs.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).