[Top][All Lists]

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

Re: GOP-PROP 9: behavior of make doc

From: Phil Holmes
Subject: Re: GOP-PROP 9: behavior of make doc
Date: Wed, 10 Aug 2011 18:36:25 +0100

----- Original Message ----- From: "Graham Percival" <address@hidden>
To: "Phil Holmes" <address@hidden>
Cc: "Keith OHara" <address@hidden>; <address@hidden>
Sent: Wednesday, August 10, 2011 4:25 PM
Subject: Re: GOP-PROP 9: behavior of make doc

On Wed, Aug 10, 2011 at 03:51:15PM +0100, Phil Holmes wrote:
So I nuked build, started again, and make doc
failed.  I've just nuked build, pulled and am running make.  I'll
let you know...

If that happens again, please keep it and report any error
messages you can find -- although we're still discussing the
"issues priorities" GOP question, there doesn't seem to be any
disagreement that failing to build from a clean build tree should
be a Critical issue.

- Graham

It happened again ... BUT ...

I think it was my fault for having a file named learning.texi in my git/Documentation directory - I think it was one of my experiments. Just deleted it and continuing make doc.

This does raise 2 issues: 1) nuking build and abort changes and pull isn't guaranteed to get a clean system. To be properly clean, you'd have to nuke git as well. 2) The error message isn't too helpful:

cd ./out-www; texi2pdf -I ./out-www -I /home/phil/lilypond-git/build/Documentation/out -I /home/phil/lilypond-git/Documentation -I /home/phil/lilypond-git/Documentation --quiet learning.texi
/usr/bin/texi2dvi: pdfetex exited with bad status, quitting.
make[2]: *** [out-www/learning.pdf] Error 1
rm out-www/weblinks.itexi
make[2]: Leaving directory `/home/phil/lilypond-git/build/Documentation'
make[1]: *** [WWW-1] Error 2
make[1]: Leaving directory `/home/phil/lilypond-git/build'
make: *** [doc-stage-1] Error 2

This is because of the --quiet option in texi2pdf (not my doing, I think). My tip from this. texi2pdf also produces a logfile, so to find what it's complained about, open learning.log and see what it says.

Phil Holmes

reply via email to

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