all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "Sören Tempel" <soeren@soeren-tempel.net>
Cc: 65486-done@debbugs.gnu.org, Christopher Baines <mail@cbaines.net>
Subject: [bug#65486] [PATCH] syscalls: Add support for musl libc
Date: Mon, 23 Oct 2023 12:11:39 +0200	[thread overview]
Message-ID: <87fs21hcmc.fsf@gnu.org> (raw)
In-Reply-To: <87il89yugy.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun, 17 Sep 2023 12:17:33 +0200")

Hello,

Ludovic Courtès <ludo@gnu.org> skribis:

> Oooh, now I remember why I ended up not applying the previous
> syscalls.scm patch: OpenJDK and a bunch of other things depend on it, so
> changing syscalls.scm entails lots of rebuilds.  (Really, they shouldn’t
> depend on it in the first place, IMO.)

This is now fixed (see <https://issues.guix.gnu.org/66525>), and I’m
happy to report that your patches have finally been pushed!

Thanks,
Ludo’.




      parent reply	other threads:[~2023-10-23 10:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-24  6:33 [bug#65486] [PATCH] syscalls: Add support for musl libc soeren
2023-09-09 13:04 ` [bug#65486] [PATCH v2] " soeren
2023-09-11 21:09   ` [bug#65486] [PATCH] " Ludovic Courtès
2023-09-13 10:23     ` Sören Tempel
2023-09-13 20:39       ` Ludovic Courtès
2023-09-15 10:57         ` Sören Tempel
2023-09-17 10:14           ` bug#65486: " Ludovic Courtès
2023-09-17 10:17           ` [bug#65486] " Ludovic Courtès
2023-09-17 11:38             ` Christopher Baines
2023-09-17 15:21             ` [bug#65486] [PATCH v3] syscalls: Consistently use existing linux? definition soeren
2023-09-17 15:21               ` [bug#65486] [PATCH v3] syscalls: Add support for musl libc soeren
2023-09-30 10:16             ` [bug#65486] [PATCH] " Sören Tempel
2023-10-10 17:15               ` Christopher Baines
2023-10-23 10:11             ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fs21hcmc.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=65486-done@debbugs.gnu.org \
    --cc=mail@cbaines.net \
    --cc=soeren@soeren-tempel.net \
    /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.