[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 2.19.31 doesn't build the docu

From: James
Subject: Re: 2.19.31 doesn't build the docu
Date: Tue, 10 Nov 2015 18:20:24 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0


On 10/11/15 17:42, Thomas Spuhler wrote:
> I just tried to build 2.19.31 but it failed in the docu section. I don't get 
> much info about the error.
> This is about all I can see:
> langdefs.py: warning: lilypond-doc gettext domain not found.
> mkdir -p out
> touch out/ly-snippets.dep
> cd ./out && 
> /home/spuhler/MageiaSVN/lilypond/BUILD/lilypond-2.19.31/scripts/build/out/run-
> and-check 
> "/home/spuhler/MageiaSVN/lilypond/BUILD/lilypond-2.19.31/out/bin/lilypond --
> verbose /home/spuhler/MageiaSVN/lilypond/BUILD/lilypond-2.19.31/ly/generate-
> documentation" "generate-documentation.log"
> Please check the logfile generate-documentation.log for errors
> GNUmakefile:295: recipe for target 'out/internals.texi' failed
> make[1]: *** [out/internals.texi] Error 1
> see build log 
> http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20151110150343.spuhler.valstar.12034/log/lilypond-2.19.31-1.mga6/build.0.20151110150405.log
> 2.19.30 builds fine
Did you clean your tree for 2.19.30 before you built 2.19.31?

Remember that we check in to staging and as long as we can make, make
check (after a make test-baseline) AND a make doc then it gets pushed to
the master tree.

I have built doc for 2.19.31 for the last two patch submissions
(yesterday) so I am pretty certain it is OK and perhaps your tree is dirty.

I don't know how you build but assuming you make a build dir and make an
'out of tree build' can you rm your build, and perhaps run

./autogen.sh && make distclean

and then try again?

Also it says to check the file '


and while the logs are not always obvious - the documentation build
process is quite complex - the files that get reported as more useful
than what is sent to the console.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]