Ludovic Courtès wrote:
Hi,
Andrew Whatson skribis:
Comparing hex dumps of the files, there are significant differences,
and a quick dive through the image dumping code leads into VM and
garbage collector details which are over my head.
I guess patching Scheme 48 to build deterministic
Ludovic Courtès wrote:
Hi again Andrew,
It turns out that the package is not reproducible:
--8<---cut here---start->8---
$ ./pre-inst-env guix challenge scheme48-prescheme
/gnu/store/qkby7f4nr3lxlm16zmswmka5hgfs6spw-scheme48-prescheme-1.9.2 contents
John Kehayias wrote:
>
> As for the original issue here, I guess the LIBRARY_PATH and ld shadowing is
> the workaround. I don't know if that is something that can/should be
> incorporated into the libgccjit package definition or should just be handled
> by any package using it. Currently, that
On Thu, 4 Aug 2022 at 16:52, Liliana Marie Prikler
wrote:
>
> > The solution used in the package-definition in my channel is to patch
> > `comp.el` to directly reference the necessary gcc/glibc paths instead
> > of relying on the environment. This occurs in the
> > "patch-driver-options" step
Hi John, Liliana,
Sorry I haven't jumped in before now, I appreciate your efforts to
bring emacs native-comp to guix!
On Thu, 4 Aug 2022 at 04:26, Liliana Marie Prikler
wrote:
>
> while this does help insofar as I now know which snippet I forgot to
> copy, I do still think that this leaves us
* libguile/finalizers.c (finalization_pipe): Initialize.
(reset_finalization_pipe): Factored out.
(start_finalization_thread): Create the pipe immediately before
launching the thread. Ensure the pipe is cleaned up if thread creation
fails. Update the finalizer callback if thread creation
Hi,
I've reviewed the finalizer patch and made some changes to ensure that
it works correctly if pipe creation or thread creation fail.
Thread creation fails in an out-of-memory scenario, so this part can be
verified by running Guile's test-out-of-memory test case. You'll need a
libgc built
