lilypond.patchy.gra...@gmail.com writes:

> Begin LilyPond compile, commit: 8019ff784cd3aa6cc43b8eb8f29a621bc5800f5c
>
> Merged staging, now at:       f1b7a60cdb4c2f1d41329a1b3a6a01f4306f6467
>
>       Success:                ./autogen.sh --noconfigure
>
>       Success:                ../configure --disable-optimising
>
>       Success:                nice make clean -j3 CPU_COUNT=3
>
>       Success:                nice make -j3 CPU_COUNT=3
>
>       Success:                nice make test -j3 CPU_COUNT=3
>
> *** FAILED BUILD ***
>
>       nice make doc -j3 CPU_COUNT=3
>
>       Previous good commit:   8019ff784cd3aa6cc43b8eb8f29a621bc5800f5c
>
>       Current broken commit:  f1b7a60cdb4c2f1d41329a1b3a6a01f4306f6467

That would be the 2240 work.  I did a full make check and a build of the
info documentation which in my experience is pretty much the same as a
make doc but somewhat faster.  Seems that the similarity does not go
deep enough.  My guess is that translations may not be covered.

Apologies.

I'll be fixing this, but it will take several hours to make a doc build
on my current setup.  Do you have the log files for the failed runs,
perchance?

Thanks

-- 
David Kastrup


_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Reply via email to