Package: guile-3.0
Version: 3.0.4-2
Let's track this properly …
----- Forwarded message from Ludovic Courtès <l...@gnu.org> -----
Date: Fri, 05 Feb 2021 16:16:41 +0100
From: Ludovic Courtès <l...@gnu.org>
Subject: Bug#964284: guile-gnutls: update to use guile 3.0
Message-ID: <87y2g235pi....@gnu.org>
I forgot to mention that a simple workaround (that I’d recommend for
Debian) is to patch Guile >= 2.2.7 (3.0 included) like so:
diff --git a/libguile/numbers.c b/libguile/numbers.c
index 19d2b2d87..de7999861 100644
--- a/libguile/numbers.c
+++ b/libguile/numbers.c
@@ -158,7 +158,7 @@ VARARG_MPZ_ITERATOR (mpz_clear)
/* Default to 1, because as we used to hard-code `free' as the
deallocator, we know that overriding these functions with
instrumented `malloc' / `free' is OK. */
-int scm_install_gmp_memory_functions = 1;
+int scm_install_gmp_memory_functions = 0;
static SCM flo0;
static SCM exactly_one_half;
static SCM flo_log10e;
It slows down bignum-heavy applications, which are rare but include the
compiler itself¹. That’s why I’m also looking at other options.
Ludo’.
¹ https://lists.gnu.org/archive/html/guile-devel/2020-02/msg00023.html
More context:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964284#33
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964284#58
