David Kastrup writes:
[...]
I apologize for sending this and the previous mail to the Guile-devel
list in violation of my ban here. I had been of the impression that
this was copied to the LilyPond developer list rather than the Guile
developer list.
Feel free to delete it.
--
Jan Nieuwenhuizen writes:
> David Kastrup writes:
>
> Hi David,
>
>> Shouldn't we worry about switching _to_ guile-2.0 first?
>
> Are you asking for help on this?
Is there any to be had? I got a whole lot of promises from Guile
developers over the years. Basically, whenever
David Kastrup writes:
Hi David,
> Shouldn't we worry about switching _to_ guile-2.0 first?
Are you asking for help on this?
In any case, I am sure that running guix with nicely coexisting
guile-2.0, guile-2.0++ and guile-next versions can be of great help
here.
Greetings,
Jan
--
Jan
Jan Nieuwenhuizen writes:
> Hi,
>
> As per chat with Ludovic on #guile (thanks!) find attached another
> approach to allow switching incrementally from guile-2.0 to guile-2.2:
> any invalid compiled files are skipped and we continue searching the
> GUILE_LOAD_COMPILED_PATH
rom f4f53b48c1d5ff42ecc66279c3b1cfcfb09d6757 Mon Sep 17 00:00:00 2001
From: Jan Nieuwenhuizen <jann...@gnu.org>
Date: Fri, 11 Mar 2016 14:58:09 +0100
Subject: [PATCH] Skip invalid compiled file found, continue searching path.
* libguile/vm.c (load_compiled_with_vm_catch_handler,
do_try_scm_call_0): N