lilypond-devel
[Top][All Lists]
Advanced

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

Re: Problems building documentation


From: Jonathan Kulp
Subject: Re: Problems building documentation
Date: Tue, 02 Dec 2008 06:17:57 -0600
User-agent: Thunderbird 2.0.0.18 (X11/20081125)

Jonathan Kulp wrote:


It's still compiling after five minutes so I think this might have done the trick. I don't know which package was the critical one but I've added all of them to my installation script so I won't forget them next time I have to install the system. Unless I post on this thread again you can assume the problem is fixed. Thanks again,

Jon

OK it exited with error messages but I think it all built properly anyway:
----------------------------------------------------------------
ce to nonexistent node `Keyboard instruments' (perhaps incorrect
sectioning?).
/home/jon/lilypond/Documentation/fr/user/out-www//specialist.texi:19:
Menu reference to nonexistent node `Keyboard instruments' (perhaps
incorrect sectioning?).
make[4]: *** [out-www/lilypond/index.html] Error 1
make[4]: Leaving directory `/home/jon/lilypond/Documentation/fr/user'
make[3]: *** [WWW-2] Error 2
make[3]: Leaving directory `/home/jon/lilypond/Documentation/fr'
make[2]: *** [WWW-2] Error 2
make[2]: Leaving directory `/home/jon/lilypond/Documentation'
make[1]: *** [WWW-2] Error 2
make[1]: Leaving directory `/home/jon/lilypond'
make: *** [web] Error 2
-----------------------------------------------------------------

All of the .pdf versions of the docs are present but not in the
directory I expected. The html files look good, too. It took me a moment to find them here:

~/lilypond/Documentation/user/out-www/

The Program Usage manual says the files will be put in
"out-www/offline-root/", but it never made a directory by that name.  I
ran "make web" from the ~/lilypond/ directory.  Did it put the docs in
the other directory because I built them independent from compiling Lilypond?

Anyway I'm very pleased to have a successful doc build. I think I'll take Werner's suggestion and redirect the terminal output to a log file next time. Thanks for the help, guys,

Jon
--
Jonathan Kulp
http://www.jonathankulp.com





reply via email to

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