> I'm using guile 1.4 and lilypond 1.5.58 too (or actually latest cvs, > but I don't think there has been a fix).
This is strange. I downloaded Guile from the Guile Home Page under www.gnu.org via anonymous CVS, and before upgrading to 1.5.6 I had serious troubles running Lily 1.5.58 (I was not the only one). The problem seems to be in file tex/tex.scm, in the last lines: ----------------------------------------------------------------------- (define-public (tex-output-expression expr port) (display (my-eval-in-module expr this-module) port ) ) ----------------------------------------------------------------------- This is different from the same file included in Lilypond 1.4.13, which uses a different construct. In fact, `my-eval-in-module' is defined to be 'eval', and Guile 1.4.1 does not accept a double-argumented `eval' (at least, *my* Guile 1.4.1 does not accept it). If I run guile from the command line and write ----------------------------------------------------------------------- (eval '(* 7 3) (current-module)) ----------------------------------------------------------------------- this will not be accepted by Guile 1.4.1 (which refuses the `(current-module)' in the statement), but it will print the correct result (21) with Guile 1.5.6. The documentation included with Guile 1.5.6 states this (it is explicitly said it is a `backward incompatible change' in the `eval' syntax). Could you please take a look at your tex.scm file? And, please, could you try the previous example under Guile? If this works on your computer, I suspect there something strange in mine... Bye Maurizio _______________________________________________ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
