Hello, On 11/11/15 14:55, Thomas Spuhler wrote: > On Wednesday, November 11, 2015 01:45:45 PM James wrote: >> Thomas, >> >> On 10/11/15 21:23, Thomas Spuhler wrote: >>> On Tuesday, November 10, 2015 10:15:22 PM Thomas Morley wrote: >>>> 2015-11-10 21:40 GMT+01:00 Thomas Spuhler <thomas.spuh...@btspuhler.com>: >>>>> On Tuesday, November 10, 2015 06:20:24 PM you wrote: >>>>>> Thomas, >>>>>> >>>>>> 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/ >>>>>>> o >>>>>>> ut/ >>>>>>> run- and-check >>>>>>> "/home/spuhler/MageiaSVN/lilypond/BUILD/lilypond-2.19.31/out/bin/lilyp >>>>>>> o >>>>>>> nd >>>>>>> -- 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/2015 >>>>>>> 1 >>>>>>> 110 >>>>>>> 150343.spuhler.valstar.12034/log/lilypond-2.19.31-1.mga6/build.0.20151 >>>>>>> 1 >>>>>>> 101 >>>>>>> 50405.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 ' >>>>>> >>>>>> generate-documentation.log >>>>>> >>>>>> 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. >>>>>> >>>>>> James >>>>> Hi James: >>>>> It's a build system for our distro (Mageia.org) and a similar on my >>>>> local >>>>> box. The tree is automatically cleaned, reps. deleted before the build. >>>>> I >>>>> cannot find a generate-documentation.log file in the build dir. >>>>> >>>>> The build part of the spec file looks >>>>> >>>>> BTW we are using guile-2.0.11 since guile 1.8 will soon be gone. (next >>>>> time it will not build on the Builds Server.) But so did we 2.19.30 >>>> Hi Thomas, >>>> >>>> not sure, but your problem may be caused by a recent patch of mine, >>>> using define*-public and an optional agument. >>>> Which is broken in guilev2. >>>> >>>> A correction is already on review. >>>> >>>> If this is indeed the problem, it will be cured soon. >>> Nice. Hopefully this is it. AS I said 2.19.30 builds >> Doesn't the 'configure' script print out a message telling you that you >> are using an 'incompatible' version of Guile when it goes through its >> checks? >> >> James > It does when I run the config manually. There is a way to get around it. > If it >2.19.30 doesn't build the doc anymore with guile2 then we may just > will > not distribute the documentation package. > What does 'documentation package' mean exactly?
Guile2 is not specific to the building of the documentation as far as I am aware. You cannot compile LilyPond without 'most' of the doc building dependencies being installed - I don't pretend to know which ones specifically but I don't think it is as simple as that. I am hoping other devs will chip in here. James _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
