Christopher Baines writes: > Ludovic Courtès writes: > >> Glad you manage to get more info. >> >> Christopher Baines skribis: >> >>> Following up on this, I've built Guile on core-updates with libgc@7 >>> rather than libgc@8 (which is what's used above), and I can't reproduce >>> the issue. So, I'm getting more certain that this is a regression which >>> the libgc upgrade has led to. >> >> Bah. :-/ >> >> We noticed similar issues with libgc@8 earlier but it seemed to be >> fixed: >> >> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=36812 >> >>> Would it be feasible to keep guile, or at least the guile Guix uses with >>> libgc@7 for now? >> >> Yes, we can define a Guile variant in (gnu packages guile) and have >> (guix self) refer to it. > > I've sent a patch which I think does this now [1]. Assuming I've done > the right thing, is this something that can be merged in to core-updates > Marius? > > 1: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=40684 > > I've tested the patch by running: > > ./pre-inst-env guile build-aux/compile-as-derivation.scm "$PWD" > > Then taking the Guix I get, and trying the script to reproduce the issue > through the guix repl, and it seems to work. I've merged the fix [1] in now, and it looks to have worked [2]. 1: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=40684 2: https://guix-patches-data.cbaines.net/revision/cef392f3936922b7b0b74bd59be67e660c10db67 Thanks for your help in resolving this Ludo!