Re: broken doc build (orchestra.ly)

[David Kastrup]

Knut Petersen <address@hidden> writes:

> Hi everybody!
>
> Building the current git lilypond binary succeeds, but building the
> documentation is broken even if I try a single core build.
>
>
> exec ./autogen.sh --noconfigure in /home/knut/sources/lily
> ... succeeded after 1 seconds
> exec ../configure --prefix=/home/knut/sources/lilybuilt/ in
> /home/knut/sources/lily/build ... succeeded after 4 seconds
> exec make -j 11 CPU_COUNT=11 LANGS='de' all in
> /home/knut/sources/lily/build ... succeeded after 71 seconds
> exec make -j 11 CPU_COUNT=11 LANGS='de' install in
> /home/knut/sources/lily/build ... succeeded after 1 seconds
> exec make -j 1 CPU_COUNT=1 LANGS='de' doc in
> /home/knut/sources/lily/build ... failed
>
> tail of build log:
> =========
>
> /home/knut/sources/lily/build/scripts/build/out/run-and-check
> "/home/knut/sources/lily/build/out/bin/lilypond -dpreview
> -dresolution=150 -o ./out-www
> /home/knut/sources/lily/Documentation/ly-examples/orchestra.ly"
> "orchestra.preview.log"
>
> Please check the logfile orchestra.preview.log for errors

Did you check that file?

> /home/knut/sources/lily/./Documentation/ly-examples/GNUmakefile:17:
> recipe for target 'out-www/orchestra.png' failed
> make[3]: *** [out-www/orchestra.png] Error 1
> make[3]: Leaving directory
> '/home/knut/sources/lily/build/Documentation/ly-examples'
> /home/knut/sources/lily/./Documentation/GNUmakefile:230: recipe for
> target 'out-www/ly-examples' failed
> make[2]: *** [out-www/ly-examples] Error 2
> make[2]: Leaving directory '/home/knut/sources/lily/build/Documentation'
> /home/knut/sources/lily/stepmake/stepmake/generic-targets.make:166:
> recipe for target 'WWW-1' failed
> make[1]: *** [WWW-1] Error 2
> make[1]: Leaving directory '/home/knut/sources/lily/build'
> /home/knut/sources/lily/stepmake/stepmake/generic-targets.make:182:
> recipe for target 'doc-stage-1' failed
> make: *** [doc-stage-1] Error 2
>
>
> ./build/Documentation/ly-examples/orchestra.preview.log
> ==================================
> GNU LilyPond 2.19.43
> Changing working directory to: `./out-www'
> Processing `/home/knut/sources/lily/Documentation/ly-examples/orchestra.ly'
> Parsing...
> Interpreting music...ERROR: Wrong type (expecting exact integer): TabVoice
>
> System:
> =====
>
> openSuSE 13.2 (x86_64)

There is no TabVoice in orchestra.ly, and orchestra.ly does not include
other files as far as I can see.  That would suggest that LilyPond is
getting fed some scraps not belonging in the file.  Or misinterpreting
some input.

Can you try running this with -dverbose (which might or might not give a
usable backtrace)?

The error occurs during the interpretation of music, so we are talking
about some property being set to symbol or string TabVoice rather than
an integer.

There is actually not a lot of opportunity in LilyPond proper for this
to happen:

address@hidden:/usr/local/tmp/lilypond$ git grep TabVoice origin ly scm lily
origin:ly/engraver-init.ly:  \name "TabVoice"
origin:ly/engraver-init.ly:  \description "Context for generating tablature. It 
accepts only @code{TabVoice}
origin:ly/engraver-init.ly:  \accepts "TabVoice"
origin:ly/engraver-init.ly:  \defaultchild "TabVoice"
origin:ly/performer-init.ly:  \name TabVoice
origin:ly/performer-init.ly:  \accepts TabVoice
origin:ly/performer-init.ly:  \defaultchild TabVoice
origin:ly/property-init.ly:  \override 
TabVoice.TabNoteHead.details.tied-properties.break-visibility = #all-invisible
origin:ly/property-init.ly:  \override 
TabVoice.TabNoteHead.details.tied-properties.parenthesize = ##f
origin:ly/property-init.ly:  \override 
TabVoice.TabNoteHead.details.repeat-tied-properties.note-head-visible = ##f
origin:ly/property-init.ly:  \override 
TabVoice.TabNoteHead.details.repeat-tied-properties.parenthesize = ##f
origin:ly/property-init.ly:  \override 
TabVoice.TabNoteHead.details.tied-properties.break-visibility = 
#begin-of-line-visible
origin:ly/property-init.ly:  \override 
TabVoice.TabNoteHead.details.tied-properties.parenthesize = ##t
origin:ly/property-init.ly:  \override 
TabVoice.TabNoteHead.details.repeat-tied-properties.note-head-visible = ##t
origin:ly/property-init.ly:  \override 
TabVoice.TabNoteHead.details.repeat-tied-properties.parenthesize = ##t

All those do not look like candidates for sneaking a symbol "TabVoice"
where it does not belong.

And in ly-examples itself, there is only

origin:Documentation/ly-examples/tab-example.ly:      \context TabVoice = 
"upper tab" { \clef "moderntab" \voiceOne \upper }
origin:Documentation/ly-examples/tab-example.ly:      \context TabVoice = 
"lower tab" { \clef "moderntab" \voiceTwo \lower }

which also does not really suggest syntax slipping a symbol into strange
contexts.

So there really is a lot of "Huh?" involved here.  Can you reproduce
this by running LilyPond _only_ on the given file?

-- 
David Kastrup