lilypond-user
[Top][All Lists]
Advanced

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

Re: Building Lily


From: Tapio Tuovila
Subject: Re: Building Lily
Date: Wed, 08 Dec 2004 10:31:08 +0200
User-agent: Mozilla Thunderbird 0.9 (X11/20041104)

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
address@hidden
http://lists.gnu.org/mailman/listinfo/lilypond-user







reply via email to

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