[Top][All Lists]

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

Re: 1.4.7 building on cygwin

From: Gerrit P. Haase
Subject: Re: 1.4.7 building on cygwin
Date: Sat, 22 Sep 2001 22:52:34 +0200

Jan Nieuwenhuizen schrieb am 2001-09-22, 20:40:

>"Gerrit P. Haase" <address@hidden> writes:
>> It is tetex not miktex included  (tetex is in the standard PATH settings and
>> if one makes use of it, it is set up correct).
>BTW, the documentation in the second attempt builds fine, maybe the
>'--with-kpathsea' flag to ./configure makes a difference. %%%
>There's a bug in the configure script wrt --with-kpathsea.  (We'll
>have to fix this some time).  If you select --with-kpathsea, you
>actually disable kpathsea (you'll see: checking whether to use
>kpathsea... no).  So, if you can't build with kpathsea, there's a
>problem with your kpathsea setup.  What errors do you get?  --jcn

Well, the build dies with make error at the end when it comes to the
Documentation directory. (This is from the log of make install, have overwritten
the old log.make, but the error is the same):

make[2]: Entering directory 
cd ./out && ../../.././lily/out/lilypond ../../.././ly/generate-documentation
GNU LilyPond 1.4.7      0 [main] lilypond 604 handle_exceptions: Error while 
dumping state (probably corrupted stack)
Signal 11
make[2]: *** [out/lilypond-internals.nexi] Error 139
make[2]: Leaving directory 
make[1]: *** [install] Error 2
make[1]: Leaving directory 

The problem is here because lilypond is called and it always dies
immediately with a stackdump.

In the last build it looks like this:

make[2]: Entering directory 
cd ./out && ../../.././lily/out/lilypond ../../.././ly/generate-documentation
GNU LilyPond 1.4.7
Now processing: `../../.././ly/'

What is strange about this is: I'm not able to run lilypond
after building. Always getting stackdumps.
But during the build it runs fine.
Also I'm getting no errors when it runs in gdb.

I suggest that there is a problem with some environment settings or other trivial like this, but I don't know yet.



reply via email to

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