[Top][All Lists]

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

Re: lilypond build on cygwin stucks

From: Gerrit P. Haase
Subject: Re: lilypond build on cygwin stucks
Date: Sun, 16 Sep 2001 19:22:59 +0200

Jan Nieuwenhuizen schrieb am 2001-09-16, 11:52:

>"Gerrit P. Haase" <address@hidden> writes:
>> I got compiletime errors:
>> =========================
>> rm -f ./out/kpath.dep; DEPENDENCIES_OUTPUT="./out/kpath.dep ./out/kpath.o" 
>> g++ -c  -DHAVE_
>> CONFIG_H  -DSTRING_UTILS_INLINED -Iinclude -I./out -I.././lib/include 
>> -I../lib/./out -I../
>> ./flower/include -I../flower/./out -I../flower/include -O2 
>> -finline-functions -g     -O2 -
>> finline-functions -g   -DSTRING_UTILS_INLINED -I/usr/local/include -Wall  -W 
>> -Wmissing-pro
>> totypes -Wconversion -o out/kpath.o
>> In file included from /usr/include/kpathsea/kpathsea.h:27,
>>                  from
>> /usr/include/kpathsea/getopt.h:99: redefinition of `struct option'
>> /usr/include/getopt.h:46: previous definition here
>> /usr/include/kpathsea/getopt.h:128: declaration of C function `int 
>> getopt_long(int, char *
>> const *, const char *, const option *, int *)' conflicts with
>> /usr/include/getopt.h:56: previous declaration `int getopt_long(int, char 
>> **, char *, opti
>> on *, int *)' here
>That's strange.  /usr/include/getopt.h should not get included at
>all.  You should check who's doing that, eg add a #warning to the top
>getopt.h and recompile, see what happens.
>> In function `class String ly_scm2string(scm_unused_struct *)':
>> passing `int *' as argument 2 of 
>> `gh_scm2newstr(scm_unused_struct *, size_t *)' changes signedness
>> make[1]: *** [out/lily-guile.o] Error 1
>> make[1]: Leaving directory `/perl/stuff/sound/lilybuild/lilypond-1.4.7/lily'
>> make: *** [all] Error 2
>Are you using a newer guile?  LilyPond 1.5.2 has seen fixes for latest
>(at that time) cvs guile, that won't be backported to lily-1.4.

I used guile-1.4 to at buildtime.
I'm trying to build guile-1.5.2 with dll's, but it doesn't work yet.

>You should use guile 1.3.4 or guile 1.4 with lilypond-1.4.  Patches to
>compile guile for cygwin are in the cygwin-cross package.

Ah, the patches doesn't fit here. There are only some related to
cross-compiling stuff.
But the problem with net_db.c and and_let*.scm are not adressed.
I will try to send my patch so everyone on cygwin should succeed
to compile guile-1.4 without errors.
Another problem is that i would like to include libregex automagically
so the user simply can do 'configure; make; make install' after patching.
Another solution would be to distribute a patched source like usual for cygwin.



reply via email to

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