I suspect this is a bug related to writing chord names under Mac OS X
10.4.10, as the topic was discussed earlier, but I thought I should
check here for confirmation:
When I run the following example, from the LilyPond 2.11.33 User
Manual, sec. 7.2.1, p. 117 (PDF p. 126):
twoWays = \transpose c c' {
\chordmode {
c1 f:sus4 bes/f
}
<c e g>
<f bes c'>
<f bes d'>
}
<<
\new ChordNames \twoWays
\new Voice \twoWays >>
in LilyPond 2.11.33, I get the errors:
Interpreting music...
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to `test2.ps'...
`cd /var/tmp/tmp.0.hcPYWo && fondu -force '/Library/Fonts/Verdana''
failed (256)
programming error: Parsed object should be dead: static
scm_unused_struct* Prob::mark_smob(scm_unused_struct*)
continuing, cross fingers
programming error: Parsed object should be dead: static
scm_unused_struct* Context_def::mark_smob(scm_unused_struct*)
continuing, cross fingers
programming error: Parsed object should be dead: static
scm_unused_struct* Lily_lexer::mark_smob(scm_unused_struct*)
continuing, cross fingers
programming error: Parsed object should be dead: static
scm_unused_struct* Grob::mark_smob(scm_unused_struct*)
continuing, cross fingers
error: failed files: "test2.ly"
If I comment out the line starting with "\new ChordNames", then it
compiles. But then the chord names are not printed out.
Is there a workaround?
Hans Åberg
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
