Updates:
        Cc: [email protected]

Comment #14 on issue 1349 by [email protected]: Guile 2.0 compat: Scheme macros must be defined/autocompiled before they are used.
http://code.google.com/p/lilypond/issues/detail?id=1349

Hi,
I've been doing some testing in conjunction with Issue 1686. I can get all the files to load OK in the call from ly_c_init_guile (where lily.scm itself is loaded) but it then fails in the later call to lilypond-main in lily.scm.

Here's the tail of a --verbose run. At the moment it fails with both Guile 1.8 and 2.0.

Building font database...

Processing `test.ly'
Parsing...
[/home/ian/src/lilypond/build/out/share/lilypond/current/ly/init.ly
[/home/ian/src/lilypond/build/out/share/lilypond/current/ly/declarations-init.ly [/home/ian/src/lilypond/build/out/share/lilypond/current/ly/music-functions-init.ly]
  [/home/ian/src/lilypond/build/out/share/lilypond/current/ly/toc-init.ly
/home/ian/src/lilypond/build/out/share/lilypond/current/ly/toc-init.ly:25:33: error: syntax error, unexpected MARKUP_FUNCTION, expecting SCM_IDENTIFIER or SCM_TOKEN
  tocTitleMarkup = \markup \huge
                                 \column {
/home/ian/src/lilypond/build/out/share/lilypond/current/ly/toc-init.ly:27:4: error: unknown escaped string: `\hspace'

    \hspace #1
/home/ian/src/lilypond/build/out/share/lilypond/current/ly/toc-init.ly:28:2: error: syntax error, unexpected '}', expecting '='

  }
/home/ian/src/lilypond/build/out/share/lilypond/current/ly/toc-init.ly:29:37: error: syntax error, unexpected '{', expecting SCM_IDENTIFIER or SCM_TOKEN
  tocItemMarkup = \markup \fill-line
                                     {
ERROR: In procedure apply:
ERROR: Wrong type argument in position 1: #<undefined>
ian@nanny-ogg:~/src/lilypond/build$

I've put the current patch for this and T1686 on Rietveld as
http://codereview.appspot.com/4760049.
Any ideas for progressing with this would be appreciated, as otherwise I'm stuck at the moment.

Cheers, Ian Hulin




_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Reply via email to