From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: Janneke Nieuwenhuizen <janneke@gnu.org>
Cc: 73181@debbugs.gnu.org
Subject: bug#73181: guix-daemon fails when invoking ‘guix authenticate’ on the Hurd
Date: Tue, 10 Dec 2024 09:07:43 +0100 [thread overview]
Message-ID: <87plm0j700.fsf@inria.fr> (raw)
In-Reply-To: <878qssbq9b.fsf@gnu.org> (Janneke Nieuwenhuizen's message of "Fri, 06 Dec 2024 19:49:52 +0100")
Hi Janneke,
Janneke Nieuwenhuizen <janneke@gnu.org> skribis:
> So, the problem is that our patch doesrn't disable the warnings after all.
> The guile-launcher has
>
> guile-launcher.c:
>
> #if defined __GNU__
> /* XXX: On 32-bit GNU/Hurd (i586-gnu), libgc emits "Repeated allocation"
> warnings that are annoying and interfere with communications between
> 'guix-daemon' and 'guix authenticate':
> <https://issues.guix.gnu.org/73181>. Silence them. */
> std::cerr << "silencing libgc warnings" << std::endl;
> GC_set_warn_proc (no_warnings);
> #endif
> ..
> scm_boot_guile (argc, argv, inner_main, 0);
>
>
> and then guile's gc.c just undoes that
D’oh! Good catch!
> From c555134310728360cb3b12472e8d487421d57a7d Mon Sep 17 00:00:00 2001
> Message-ID: <c555134310728360cb3b12472e8d487421d57a7d.1733509997.git.janneke@gnu.org>
> From: Janneke Nieuwenhuizen <janneke@gnu.org>
> Date: Fri, 6 Dec 2024 16:25:54 +0100
> Subject: [PATCH] gnu: guile-3.0: Silence GC warnings on the Hurd.
>
> * gnu/packages/patches/guile-hurd-silence-gc-warnings.patch: New file.
> * gnu/local.mk (dist_patch_DATA): Register it.
> * gnu/packages/guile.scm (guile-3.0): When building for the Hurd, use it in
> new stage "patch-silence-gc-warnings".
>
> Change-Id: I48f2641a162c3fab15655293e10c4aa2200d5843
You’ll hate me for suggesting that :-) but what if in ‘guile-launcher.c’
we moved the ‘GC_set_warn_proc’ call to ‘inner_main’? I believe in that
case it would have the desired effect, right?
That would avoid patching Guile wholesale.
Anyhow, kudos for the tricky and probably lengthy debugging session!
Thanks,
Ludo’.
next prev parent reply other threads:[~2024-12-10 8:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 15:40 bug#73181: guix-daemon fails when invoking ‘guix authenticate’ on the Hurd Ludovic Courtès
2024-09-11 17:08 ` Ludovic Courtès
2024-10-31 19:14 ` janneke
2024-11-04 8:21 ` Ludovic Courtès
2024-11-05 11:26 ` janneke
2024-11-05 14:03 ` Ludovic Courtès
2024-11-05 15:41 ` janneke
2024-11-10 11:54 ` Ludovic Courtès
2024-11-10 12:01 ` janneke
2024-11-18 8:41 ` janneke
2024-12-06 18:49 ` Janneke Nieuwenhuizen
2024-12-10 8:07 ` Ludovic Courtès [this message]
2024-12-10 12:47 ` Janneke Nieuwenhuizen
2024-12-10 13:53 ` Ludovic Courtès
2024-12-10 14:02 ` Janneke Nieuwenhuizen
2024-12-10 17:00 ` Janneke Nieuwenhuizen
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=87plm0j700.fsf@inria.fr \
--to=ludovic.courtes@inria.fr \
--cc=73181@debbugs.gnu.org \
--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).