Re: broken doc build (orchestra.ly)

[James]

Knut,

On 20/05/16 10:34, Phil Holmes wrote:
> ----- Original Message ----- From: "Knut Petersen" 
> <address@hidden>
> To: <address@hidden>
> Sent: Friday, May 20, 2016 9:56 AM
> Subject: broken doc build (orchestra.ly)
>
>
> > 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
> >
> > /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)
>
>
> This looks very much like the problem James is experiencing with 
> patchy.  I don't think the problem file is likely to be orchestra.ly, 
> since that has no tabs in it.  It compiles cleanly on my Windows 
> system.  tab-example.ly does have tabs and produces errors on my 
> system, whilst still completing:
>
> programming error: mis-predicted force, 99.584646 ~= 100.503145
> continuing, cross fingers
>
> James: could you try compiling the tab example on your machine and see 
> what it gives?

Yes this is exactly the same problem I have been getting the last week 
or so both on Fedora and Ubuntu.

See my emails

http://lists.gnu.org/archive/html/lilypond-devel/2016-05/msg00093.html

So the problem is probably not distribution related and I a not 
convinced it is file related either.

Note that you can probably run the reg tests and the reg test check too 
even though this make doc fails like this. I have not been able to 
isolate the cause but since this morning, it seems this problem has gone 
away for me.

I ended up just removing my entire $LILYPOND_GIT dir and cloning it all 
again. Although I am sure I did that previously, but since doing that 
I've been able to get a successful make doc. I thought at first that it 
was a multi core issue (as sometimes it does happen) and was able to get 
-j4 working when -j5+ didn't, but I've just done three or four patches 
today and all using -j7 and it worked without issue.

The only difference if you can call it that is that the only thing that 
had changed from git's point of view that I can see was Phil's checkins 
that he does prior to the release of unstable.

I don;t know what the lilypond.pot stuff does but could that have been 
the problem?

James