Re: Guile 1.5.x
I don't understand. I'm using Guile 1.4, and it's fine for LilyPond 1.4.13 and 1.4.58. Maybe there are modified versions of Guile around, or maybe there's a problem with Guile 1.4.1? What lilypond version are you using, what guile version, and where did you get your guile? Jan. Yes, you are right. In fact, I had no problems running version 1.4.13. The error messages came when I installed Lily 1.5.58 (NOT 1.4.58 as I said in my message --- this was a typo...). Yesterday there was a little discussion about that, and in my last e-mail I forgot to specify again what I was talking about. Maurizio ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Guile 1.5.x
Maurizio Tomasi [EMAIL PROTECTED] writes: Just a little note to let you know that the problems noted by Simon (bad syntax of the `eval' command) is due to the different `eval' syntax in Guile 1.4.x. Yesterday I installed Guile 1.5.6 on my home computer, and any problem disappeared. Perhaps somebody should correct `INSTALL.txt' (in Lilypond 1.5.58), since this text says that Guile 1.4.x is fine for Lily. I don't understand. I'm using Guile 1.4, and it's fine for LilyPond 1.4.13 and 1.4.58. Maybe there are modified versions of Guile around, or maybe there's a problem with Guile 1.4.1? What lilypond version are you using, what guile version, and where did you get your guile? Jan. -- Jan Nieuwenhuizen [EMAIL PROTECTED] | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Guile 1.5.x
i installed guile-1.5.6 yesterday, and had a compilation error when i tried recompiling lilypond. i think that was to do with cached config-files. i started with a fresh code tree, and am now compiling lilypond again. it may take a while to finish (old machine), but i'll keep you posted. greetings, simon. On Wed, 2002-05-29 at 11:23, Maurizio Tomasi wrote: Just a little note to let you know that the problems noted by Simon (bad syntax of the `eval' command) is due to the different `eval' syntax in Guile 1.4.x. Yesterday I installed Guile 1.5.6 on my home computer, and any problem disappeared. Perhaps somebody should correct `INSTALL.txt' (in Lilypond 1.5.58), since this text says that Guile 1.4.x is fine for Lily. Bye Maurizio ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user -- Confucius say, man who live in glass house shower in basement. ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Guile 1.5.x
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
Re: Guile 1.5.x
Maurizio Tomasi [EMAIL PROTECTED] writes: In fact, `my-eval-in-module' is defined to be 'eval' This is wrong. For guile 1.5.x, it should be set to eval-in-module. Hmm. What does guile -c '(write (minor-version))' say? I suspect it says 4.1, and that's why you're seeing this problem. Could you try in scm/tex.scm, at: (define my-eval-in-module eval) (if (or (equal? (minor-version) 4) (equal? (minor-version) 3.4)) (begin (set! my-eval-in-module eval-in-module) )) adding (equal? (minor-version) 4.1), like so: (define my-eval-in-module eval) (if (or (equal? (minor-version) 4) (equal? (minor-version) 4.1) (equal? (minor-version) 3.4)) (begin (set! my-eval-in-module eval-in-module) )) -- Jan Nieuwenhuizen [EMAIL PROTECTED] | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Guile 1.5.x
[EMAIL PROTECTED] writes: 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). These reports about guile incompatibility are bogus. I've built a 1.5.58 RPM on Redhat 7.3 that uses GUILE 1.4. We added special compatibility glue to make tex.scm work with 1.4 as well. I suspect that you have different versions of guile concurrently installed, and that at runtime a different one is used than what you compiled it with. -- Han-Wen Nienhuys | [EMAIL PROTECTED]| http://www.cs.uu.nl/~hanwen/ ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Guile 1.5.x
Hmm. What does guile -c '(write (minor-version))' say? I suspect it says 4.1, and that's why you're seeing this problem. Unfortunately (!) my Lilypond system now runs well, so I erased Guile 1.4.1 from my hard disk. Thus, I cannot run this test. But I think my problem was not a real problem. Now I am sure you are right about Guile 1.4.1, Jan. In fact, I did not understand that Lilypond uses the `libguile' library, so one should rebuild the executable after upgrading Guile. Let me explain what I done. I tried to install Lilypond 1.5.58 on my system with an old version of guile installed (1.3.x), and a lot of problems arose. After having upgraded Guile to 1.4.1, I issued a `make' command, but I am not sure if make does recognize a newly installed library and thus rebuilds the executable. I should have done a `make distclean' after the guile upgrade. After this mess, I upgraded to Guile 1.5.6 and then (but only at this time!), being totally frustrated, I issued a `make distclean'... and all was right! Sorry! Anyway, I hope these notes will be useful to somebody. Thanks Maurizio ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Guile 1.5.x
Han-Wen Nienhuys [EMAIL PROTECTED] writes: These reports about guile incompatibility are bogus. I don't think so, I think these guys are using Guile 1.4.1. But this could have been stated a bit clearer. Unfortunately, what is actually Guile 1.4.0 gets called Guile 1.4, and in addition, Guile has the utterly silly convention of lumping the patch-level together with the minor-version. A fix is in CVS. Although we should probably check on functionality (existence of a function, eg 'eval-in-module) rather than a version number. Jan. -- Jan Nieuwenhuizen [EMAIL PROTECTED] | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
