On Tue, 2018-02-20 at 12:34 +0000, Richard Shann wrote:
> [...]
> I ran the executable on a Windows laptop under Vista. The first error
> reported was a failure to make the temp directory, although it had
> actually created it - I've added some debug output for that.
> But then guile crashed consistently trying to execute the scheme
> procedure (load-module ...). 
I have found out why a crash in libguile was occurring - it was the
setting of LD_LIBRARY_PATH (or windows equivalent) which meant it found
a version of libguile below C:\Program Files\Denemo, once I hid that
path it could load denemo.scm. My guess is that Denemo is adding the
new path after the one added during previous installs :( The behavior
was then similar to the wine run,

However it gave this error message:


Denemo -         ?[0m: System wide denemo.scm

Denemo -         ?[0m:
                   A script error for file/script
F:\denemo\share\denemo\actions\denemo.scm; the throw arguments are

(dynamic-link file: ~S, message: ~S (libguile-srfi-srfi-1-v-3 The
specified module could not be found.) #f)
Denemo -         ?[0m:
                   The tag is



and the generation of PDF via LilyPond failed with the scheme procedure
FinalizeTypesetting not found (it is defined in denemo.scm)

This was done with the version of denemo built 21/2/2018 18:58

It prints out the correct path to the temp file on start up but still
reports that it failed to create it.


Denemo-devel mailing list

Reply via email to