Okay, with careful attention and speedy ctrl-c'ing I was able to capture the following:
true make[2]: Leaving directory `/home/trinity/lilypond/src/lilypond-2.4.2/stepmake/stepmake' make[1]: Leaving directory `/home/trinity/lilypond/src/lilypond-2.4.2/stepmake' make[1]: Entering directory `/home/trinity/lilypond/src/lilypond-2.4.2/Documentation' make PACKAGE=LILYPOND package=lilypond -C user all && make PACKAGE=LILYPOND package=lilypond -C bibliography all && make PACKAGE=LILYPOND package=lilypond -C pictures all && make PACKAGE=LILYPOND package=lilypond -C topdocs all && make PACKAGE=LILYPOND package=lilypond -C misc all && true make[2]: Entering directory `/home/trinity/lilypond/src/lilypond-2.4.2/Documentation/user' LANG= makeinfo --enable-encoding -I ./out --output=./out/lilypond.info out/lilypond.nexi ./out/macros.texi:89: Unknown command `ifdocbook'. ./out/macros.texi:106: Unmatched [EMAIL PROTECTED]'. ./out/macros.texi:115: warning: macro `internalsref' previously defined. ./out/macros.texi:93: warning: here is the previous definition of `internalsref'. ./out/macros.texi:120: warning: macro `inputfileref' previously defined. ./out/macros.texi:102: warning: here is the previous definition of `inputfileref'. ./out/fdl.texi:644: @code missing close brace. ./out/fdl.texi:296: @code missing close brace. ./out/fdl.texi:296: @code missing close brace. ./out/fdl.texi:564: @code missing close brace. ./out/fdl.texi:564: @code missing close brace. ./out/fdl.texi:667: @code missing close brace. ./out/fdl.texi:668: @code missing close brace. ./out/fdl.texi:714: @code missing close brace. ./out/fdl.texi:714: @code missing close brace. ./out/fdl.texi:882: @code missing close brace. .true make[2]: Leaving directory `/home/trinity/lilypond/src/lilypond-2.4.2/stepmake/stepmake' make[1]: Leaving directory `/home/trinity/lilypond/src/lilypond-2.4.2/stepmake' make[1]: Entering directory `/home/trinity/lilypond/src/lilypond-2.4.2/Documentation' make PACKAGE=LILYPOND package=lilypond -C user all && make PACKAGE=LILYPOND package=lilypond -C bibliography all && make PACKAGE=LILYPOND package=lilypond -C pictures all && make PACKAGE=LILYPOND package=lilypond -C topdocs all && make PACKAGE=LILYPOND package=lilypond -C misc all && true make[2]: Entering directory `/home/trinity/lilypond/src/lilypond-2.4.2/Documentation/user' LANG= makeinfo --enable-encoding -I ./out --output=./out/lilypond.info out/lilypond.nexi ./out/macros.texi:89: Unknown command `ifdocbook'. ./out/macros.texi:106: Unmatched [EMAIL PROTECTED]'. ./out/macros.texi:115: warning: macro `internalsref' previously defined. ./out/macros.texi:93: warning: here is the previous definition of `internalsref'. ./out/macros.texi:120: warning: macro `inputfileref' previously defined. ./out/macros.texi:102: warning: here is the previous definition of `inputfileref'. ./out/fdl.texi:644: @code missing close brace. ./out/fdl.texi:296: @code missing close brace. ./out/fdl.texi:296: @code missing close brace. ./out/fdl.texi:564: @code missing close brace. ./out/fdl.texi:564: @code missing close brace. ./out/fdl.texi:667: @code missing close brace. ./out/fdl.texi:668: @code missing close brace. ./out/fdl.texi:714: @code missing close brace. ./out/fdl.texi:714: @code missing close brace. ./out/fdl.texi:882: @code missing close brace. ./out/fdl.texi:882: @code missing close brace. ./out/fdl.texi:945: @code missing close brace. ./out/fdl.texi:1115: @code missing close brace. ./out/fdl.texi:1115: @code missing close brace. ./out/fdl.texi:1258: @code missing close brace. ./out/fdl.texi:1258: @code missing close brace. ./out/fdl.texi:1710: @code missing close brace. ./out/fdl.texi:1711: @code missing close brace. ./out/fdl.texi:1776: @code missing close brace. ./out/fdl.texi:1818: @code missing close brace. ./out/fdl.texi:1864: @code missing close brace. /out/fdl.texi:882: @code missing close brace. ./out/fdl.texi:945: @code missing close brace. ./out/fdl.texi:1115: @code missing close brace. ./out/fdl.texi:1115: @code missing close brace. ./out/fdl.texi:1258: @code missing close brace. ./out/fdl.texi:1258: @code missing close brace. ./out/fdl.texi:1710: @code missing close brace. ./out/fdl.texi:1711: @code missing close brace. ./out/fdl.texi:1776: @code missing close brace. ./out/fdl.texi:1818: @code missing close brace. ./out/fdl.texi:1864: @code missing close brace. etc, etc, for many more lines - then the "too many errors" begins. This sure does look like a documentation error. I am game to try a make install at this point, if you think it'll work. On Wed, 08 Dec 2004 10:31:08 +0200, Tapio Tuovila wrote > Mats Bengtsson wrote: > > > The list of "Too many errors!" usually appears if you haven't upgraded > > to a very new version of texinfo. However, it only affects the > > documentation, so as long as you use the documentation on the web, > > make followed by make install should provide a perfectly useful > > installation. > > > > /Mats > > This is interesting and probably very useful information. However, > when I tried to build 2.4.2 on Suse 9.1 I had upgraded texinfo to > the newest that could be found as source code. And this "Too many > errors!" thing appeared also after succesful ./configure when plain > 'make' was tried. So I rolled backwards and found out that still > some packages that were needed for building the actual lilypond > application were missing. So I installed the missing packages and > after that the building and installing went OK. So in this case it > seemed to me it was not question about documentation. (Only my > humble view, but the situation discribed in the original message > seemed familiar, so... ;-) ) > > regards, > > Tapio > > > > > Tapio Tuovila wrote: > > > >> LinuxChiq wrote: > >> > >>> I am trying to build Lilypond 2.4.2 on Suse 9.1. I have gotten > >>> ./configure to > >>> complete without errors, but when I make all it bails with a long > >>> list of > >>> Too many errors! Gave up. > >>> > >>> I don't see an install.log - where can I find out what the problem is? > >>> > >>> Cheers, > >>> > >>> Raven > >>> > >>> > >> > >> Hi, > >> you can roll backwards your console screen, the cause of the problem > >> is being printed somewhere near the beginning of the error list. As > >> far as I recall there were some (two? three?) packages missing, even > >> if ./configure completes OK. > >> > >> But 2.4.2 can be built on Suse 9.1 OK. > >> > >> best regards, > >> > >> Tapio > >> > >> > >> _______________________________________________ > >> lilypond-user mailing list > >> [EMAIL PROTECTED] > >> http://lists.gnu.org/mailman/listinfo/lilypond-user > > > > > > _______________________________________________ > lilypond-user mailing list > [EMAIL PROTECTED] > http://lists.gnu.org/mailman/listinfo/lilypond-user -- Open WebMail Project (http://openwebmail.org) _______________________________________________ lilypond-user mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-user
