On Wed, Aug 14, 2013 at 09:35:46PM +0200, David Kastrup wrote:
> Marek Klein <ma...@gregoriana.sk> writes:
>
> > Hello David,
> > do we need a tracker issue for this?
> >
> > Marek
> >
> > 2013/8/5 David Kastrup <d...@gnu.org>
> >
> >> Thomas Klausner <t...@giga.or.at> writes:
> >>
> >> > Hi!
> >> >
> >> > The latest stable and development branches of lilypond do not compile
> >> with
> >> > the recently released bison-3.0.
> >> >
> >> > The following patch fixes this (sorry, whitespace may be off):
>
> Issue 3488, fixed already in 2.17.24
Thanks.
I've tried that but see a new error while generating documentation:
/scratch/wip/lilypond-devel/work/lilypond-2.17.24/out/share/lilypond/current/ly/chord-modifiers-init.ly:26:4:
error: syntax error, unexpected REAL
<
c e gis>1-\markup { "+" }
/scratch/wip/lilypond-devel/work/lilypond-2.17.24/out/share/lilypond/current/scm/lily.scmBacktrace:
In
/scratch/wip/lilypond-devel/work/lilypond-2.17.24/out/share/lilypond/current/scm/lily.scm:
960: {1}* (let* ((failed #)) (if (ly:get-option #) (begin #)) ...)
960: 2* [lilypond-all #]
973: 3 (let* ((failed #) (separate-logs #) (ping-log #) ...) (gc) ...)
985: 4* [for-each #<procedure #f #> #]
In unknown file:
?: 5* [#<procedure #f #>
"/scratch/wip/lilypond-devel/work/lilypond-2.17.24/ly/generate-documentation"]
In
/scratch/wip/lilypond-devel/work/lilypond-2.17.24/out/share/lilypond/current/scm/lily.scm:
987: 6* (let* (# # #) (if separate-logs #) (if ping-log #) ...)
998: 7* [lilypond-file #<procedure #f #> ...]
1033: 8 [catch ly-file-failed #<procedure #f ()> #<procedure #f (x . args)>]
In unknown file:
?: 9* [#<procedure #f ()>]
In
/scratch/wip/lilypond-devel/work/lilypond-2.17.24/out/share/lilypond/current/scm/lily.scm:
1034: 10* [ly:parse-file
"/scratch/wip/lilypond-devel/work/lilypond-2.17.24/ly/generate-documentation"]
In /scratch/wip/lilypond-devel/work/lilypond-2.17.24/ly/init.ly:
9: 11* [session-initialize #<procedure #f ()>]
In
/scratch/wip/lilypond-devel/work/lilypond-2.17.24/out/share/lilypond/current/scm/lily.scm:
131: 12 (if (ly:undead? lilypond-declarations) (begin # #) (begin # # #))
142: 13 (begin (thunk) (set! lilypond-interfaces (filter # #)) ...)
143: 14* [#<procedure #f ()>]
In /scratch/wip/lilypond-devel/work/lilypond-2.17.24/ly/init.ly:
17: 15 [ly:parser-parse-string # "\\include \"declarations-init.ly\""]
In unknown file:
?: 16* [construct-chord-elements {1} #<Duration 4 > ()]
In
/scratch/wip/lilypond-devel/work/lilypond-2.17.24/out/share/lilypond/current/scm/chord-entry.scm:
28: 17* (let* (# # # # ...) (letrec # # # ...))
In unknown file:
?: 18 (letrec (# # # # ...) (set! root #) (if # #) ...)
In
/scratch/wip/lilypond-devel/work/lilypond-2.17.24/out/share/lilypond/current/scm/chord-entry.scm:
116: 19* (set! root (ly:pitch-transpose root (ly:make-pitch {1} 0 0)))
116: 20* [ly:pitch-transpose {1} #<Pitch c'' >]
/scratch/wip/lilypond-devel/work/lilypond-2.17.24/out/share/lilypond/current/scm/chord-entry.scm:116:16:
In procedure ly:pitch-transpose in expression (ly:pitch-transpose root
(ly:make-pitch 1 0 ...)):
/scratch/wip/lilypond-devel/work/lilypond-2.17.24/out/share/lilypond/current/scm/chord-entry.scm:116:16:
Wrong type argument in position 1 (expecting Pitch): 1
Is this enough context? Does this ring a bell for someone?
> >> > While I'm here, I'll just report a minor issue too:
> >> > scripts/auxiliar/cg-section.sh uses the unportable "==" operator for
> >> > test(1), only supported by bash, not even by GNU coreutils. Please use
> >> the
> >> > portable "=" instead.
> >>
> >> Typical bashism, yes. Personally, I prefer using case/esac for almost
> >> everything. That usually is quite more flexible and has been a shell
> >> builtin for quite longer than test.
>
> I'll push a fix in the next hour as it's trivial to do so.
Thanks again,
Thomas
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
