Re: guile-1.4 shared patch (was: Re: lilypond build on cygwin stucks)
Jan Nieuwenhuizen schrieb am 2001-09-20, 9:54: >"Gerrit P. Haase" <[EMAIL PROTECTED]> writes: > >> Jan Nieuwenhuizen schrieb am 2001-09-18, 22:04: >> >> Well now, after several attempts, I got it managed to build guile on >> Cygwin with shared libs (libguile.dll & libguilereadline.dll). >> >> Now it is: guile-1.4-2. >> The patch is up (because 30K), i hope it works for others, too. >> http://familiehaase.de/cywgin/guile/guile-1.4-2.patch I have updated the patch today, because it seems the import library gets not built (and not installed ), but there is one generated when linking libguilereadline with libguile.dll so we can take this. Needs to be copied and renamed manually. I have not tried yet to link against this import lib with a libtoolized package, is there one somewhere which I can use to test the libguil.la and import-lib? ( Patch is at same location, same name). LilyPond links o.k with that importlib, i built it yesterday, needs some testing yet. >Ok, that looks good. Where did you get the autogen.sh and >autobuild.sh scripts; I mean, why do they need to be in the patch? I wrote it, parts are from the autogen.sh of current guile (1.7) and other parts are from me. autobuild.sh is just a bundle of all steps i did to get it up and running so i was able to link against libguile.dll. If you type sh -x ./autobuild.sh all should be managed by this script. If you type 'sh -x autogen.sh' only the configure and Makefile.in scripts were updated plus a new version of libtool is copied in the lt subdir. >Also, you add > > AC_LIBTOOL_WIN32_DLL > >to configure.in, that looks rather cygwin specific... That is for libtool to tell it to build win32 .dll's:) >For cross-compiling guile, we'll still need the -guile-config >patch on top of this. O.k. I don't know about problems with crosscompiling. But it should be possible to build .dll's at a linux box, though I don't know. You are talking about this: #!/bin/sh # target-guile-config.in case $1 in --version) echo "1.4" exit 0 ;; compile) echo "-I/home/cygwin/cygwin-1.3.2/usr/include -I/home/cygwin/cygwin-1.3.2/usr/include/w32api" exit 0 ;; link) echo "-lguile -L/home/cygwin/cygwin-1.3.2/usr/lib -lregex /home/cygwin/cygwin-1.3.2/usr/bin/cygwin1.dll" exit 0 ;; esac Question: = I don't need to include win32api for a 'native' cygwin build. Do you compile with -mno-cygwin flag? And you are linking against cygwin1.dll? Standard is to put the import libs on the link line (libcygwin.a). If I link against libcygwin.a I don't need w32api and vice versa. This -guile-config is of no use after it is installed on cygwin. Gerrit -- =^..^= ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: guile-1.4 shared patch (was: Re: lilypond build on cygwin stucks)
"Gerrit P. Haase" <[EMAIL PROTECTED]> writes: > Jan Nieuwenhuizen schrieb am 2001-09-18, 22:04: > > Well now, after several attempts, I got it managed to build guile on > Cygwin with shared libs (libguile.dll & libguilereadline.dll). > > Now it is: guile-1.4-2. > The patch is up (because 30K), i hope it works for others, too. > http://familiehaase.de/cywgin/guile/guile-1.4-2.patch Ok, that looks good. Where did you get the autogen.sh and autobuild.sh scripts; I mean, why do they need to be in the patch? Also, you add AC_LIBTOOL_WIN32_DLL to configure.in, that looks rather cygwin specific... For cross-compiling guile, we'll still need the -guile-config patch on top of this. Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
guile-1.4 shared patch (was: Re: lilypond build on cygwin stucks)
Jan Nieuwenhuizen schrieb am 2001-09-18, 22:04: Well now, after several attempts, I got it managed to build guile on Cygwin with shared libs (libguile.dll & libguilereadline.dll). Now it is: guile-1.4-2. The patch is up (because 30K), i hope it works for others, too. http://familiehaase.de/cywgin/guile/guile-1.4-2.patch How to build it: Requires *all* of Cygwin *plus* libtool-1.4.2 I included two scripts in the patch. Besides that, there are some minor changes in configure.in and Makefile.am scripts and some changes to get a clean build on Cygwin. First script: = 'autogen.sh' which is important. This is a *must run* to update all the Makefile.in templates and some other files. And it is a *must run* with autoconf 2.52e and automake 1.5 and libtool 1.4.2 (binary -> http://familiehaase.de/cywgin/libtool/). I bet it fails if the autotools are older. Additional instructions are at the Wiki site now: http://lilypond.org/wiki/?GuilePatch Second script: == 'autobuild.sh' There is all included so nothing else needs to be done *after* patching. The script is in the patch, so patching needs to be done at first. Put guile-1.4 source and the patch in some directory, unpack guile, bash$ cd guile-1.4 bash$ patch -p1<../guile-1.4-2.patch You may run 'sh ./autobuild.sh' now and after a while..., all should be ready & done. Please feel free to ask if there are problems. To get the resource for Pyhton, I've also built latest Python cvs source, but there will be an update of python for Cygwin soon (I hope so). Now the only thing left (for tomorrow) is building LilyPond, which requires also python & tetex plus (what I have not figured out yet) hopefully no patches. *all* is at least: cygwin, gawk, less, ncurses, sed, textutils, ash, gcc, autoconf, diff, gdb, m4, automake, make, sh-utils, bash, grep, tar, binutils crypt, fileutils, groff, patch, zlib, bison, ctags, findutils, gzip termcap, flex, inetutils, regex, texinfo, perl, ghostscript, readline *plus* is: libtool-1.4.2 Gerrit -- http://lilypond.org/wiki/?CompilingOnWindows -- =^..^= ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond build on cygwin stucks
Jan Nieuwenhuizen schrieb am 2001-09-18, 22:04: >add --exclude flags (or run make *clean) until you're patch contains >nothing you didn't type yourself. Yep, i stripped it down to 25KB. >> >Do you think shared libraries are an improvement, eg, how do you >> >intend to address the versioning issue? >> >> I called it: >> $ guile --version >> Guile 1.4-gph-1 > >I meant rather: how do you plan to install lilypond-1.4 and >lilypond-1.5 alongside eachother, when you use shared libraries. On >my box, they're linked to libguile.so.9 and libguile.so.10, resp. Well, is it needed to install two lilypond version? Why? Do they need different versions of guile? I think one (stable) version should be enough. I even don't know yet if it possible to build lily with shared libs here on cygwin. We'll see. Gerrit -- =^..^= ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond build on cygwin stucks
"Gerrit P. Haase" <[EMAIL PROTECTED]> writes: > Hmmm, there are the Makefiles included, but not much more. > The point is that I did a complete update to current autoconf, > automake, libtool. So most of the configuration files are changed. So, you'll want to exclude those from the diff. Try something like: diff -purN --exclude=*.deps --exclude=*.x -X .cvsignore ../guile.orig . add --exclude flags (or run make *clean) until you're patch contains nothing you didn't type yourself. > >Do you think shared libraries are an improvement, eg, how do you > >intend to address the versioning issue? > > I called it: > $ guile --version > Guile 1.4-gph-1 I meant rather: how do you plan to install lilypond-1.4 and lilypond-1.5 alongside eachother, when you use shared libraries. On my box, they're linked to libguile.so.9 and libguile.so.10, resp. Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond build on cygwin stucks
Jan Nieuwenhuizen schrieb am 2001-09-18, 17:26: >"Gerrit P. Haase" <[EMAIL PROTECTED]> writes: >> Well now after building as a shared version, the patch is about 2MB. > >That's rediculous. The full guile sources are about 5MB. Your patch >probably contains lots of generated files. O.k., I can strip it off down to some KB but it will work only then, if one who wants to build it has latest autotools including libtool installed. >Do you think shared libraries are an improvement, eg, how do you >intend to address the versioning issue? I don't know if it is a real improvement. I hope so. I think versioning is no problem. I will just count up the version number. You built the number one for LilyPond, lets build number two. Gerrit -- =^..^= ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond build on cygwin stucks
Jan Nieuwenhuizen schrieb am 2001-09-18, 17:26: >"Gerrit P. Haase" <[EMAIL PROTECTED]> writes: > >> Jan Nieuwenhuizen schrieb am 2001-09-17, 11:53: >> >> >"Gerrit P. Haase" <[EMAIL PROTECTED]> writes: >> [..] >> >Ok, that's fine. See my edits to the wiki. >> >> >... it is not possible to post the GuilePatch here. (Try again --jcn) >> >> That means, if I open the edit window again, the line-breaks and tabs are >> o.k. then? > >If they aren't, your web browser or form editor is broken. > >> Well now after building as a shared version, the patch is about 2MB. > >That's rediculous. The full guile sources are about 5MB. Your patch >probably contains lots of generated files. Hmmm, there are the Makefiles included, but not much more. The point is that I did a complete update to current autoconf, automake, libtool. So most of the configuration files are changed. >Do you think shared libraries are an improvement, eg, how do you >intend to address the versioning issue? I called it: $ guile --version Guile 1.4-gph-1 And the package is named: guile-1.4-gph-1-dll.tar.bz2 Gerrit -- =^..^= ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond build on cygwin stucks
"Gerrit P. Haase" <[EMAIL PROTECTED]> writes: > Jan Nieuwenhuizen schrieb am 2001-09-17, 11:53: > > >"Gerrit P. Haase" <[EMAIL PROTECTED]> writes: > [..] > >Ok, that's fine. See my edits to the wiki. > > >... it is not possible to post the GuilePatch here. (Try again --jcn) > > That means, if I open the edit window again, the line-breaks and tabs are > o.k. then? If they aren't, your web browser or form editor is broken. > Well now after building as a shared version, the patch is about 2MB. That's rediculous. The full guile sources are about 5MB. Your patch probably contains lots of generated files. Do you think shared libraries are an improvement, eg, how do you intend to address the versioning issue? Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond build on cygwin stucks
Jan Nieuwenhuizen schrieb am 2001-09-17, 11:53: >"Gerrit P. Haase" <[EMAIL PROTECTED]> writes: [..] >Ok, that's fine. See my edits to the wiki. >... it is not possible to post the GuilePatch here. (Try again --jcn) That means, if I open the edit window again, the line-breaks and tabs are o.k. then? Well now after building as a shared version, the patch is about 2MB. I think the best solution is to put it up at my homepage and post just the link. Gerrit -- =^..^= ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond build on cygwin stucks
"Gerrit P. Haase" <[EMAIL PROTECTED]> writes: > >uh, kpathsea.h includes kpatsea/getopt.h and getopt.h, which doesn't > >work. > > Not on cygwin, only kpathsea/getopt.h is included: on cygwin, getopt.h is included through unistd.h. both are unneeded, that's why you cat use the -D__GETOPT_H__ workaround. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond build on cygwin stucks
Jan Nieuwenhuizen schrieb am 2001-09-17, 21:06: >"Gerrit P. Haase" <[EMAIL PROTECTED]> writes: > >> What kind of bug do you think of? > >uh, kpathsea.h includes kpatsea/getopt.h and getopt.h, which doesn't >work. Not on cygwin, only kpathsea/getopt.h is included: Siebenschlaefer@LORELEY /usr/include/kpathsea $ rgrep getopt.h ./kpathsea.h:#include Gerrit -- =^..^= ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond build on cygwin stucks
Jan Nieuwenhuizen schrieb am 2001-09-17, 21:06: >"Gerrit P. Haase" <[EMAIL PROTECTED]> writes: > >> What kind of bug do you think of? > >uh, kpathsea.h includes kpatsea/getopt.h and getopt.h, which doesn't >work. And I saw that unistd.h now includes getopt.h by default, too. That is too bad. I use an old unistd.h where it wasn't included, I have a backup from 2001-05 so I think it is in there since cygwin-1.3.2. >> Have you offerd a fix to cygwin folks? > >No, I've only got a workaround yet, not a fix. Also, offering patches >to cygwin is a tedious process, and this is a very small thing. Hmmm, in that case it is really complex. I think I'm the first now who got problems with the include of getopt.h in unistd.h. If if also in kpathsea/kpathsea.h, this is trivial and a bug in the tetex-package. Gerrit -- =^..^= ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond build on cygwin stucks
"Gerrit P. Haase" <[EMAIL PROTECTED]> writes: > What kind of bug do you think of? uh, kpathsea.h includes kpatsea/getopt.h and getopt.h, which doesn't work. > Have you offerd a fix to cygwin folks? No, I've only got a workaround yet, not a fix. Also, offering patches to cygwin is a tedious process, and this is a very small thing. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond build on cygwin stucks
Jan Nieuwenhuizen schrieb am 2001-09-17, 14:08: Hi Jan, [...] >Ah' you're using cygwin > 1.3.2, there's a bug in the unistd.h/getopt >headers. Try I found s.th. like a bug in MY unistd.h, but i modified it myself. What kind of bug do you think of? Have you offerd a fix to cygwin folks? >CPPFLAGS="-I$PREFIX/include -I$PREFIX/include/w32api -D__GETOPT_H__" \ > ./configure --prefix=$PREFIX > Gerrit -- =^..^= ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond build on cygwin stucks
"Gerrit P. Haase" <[EMAIL PROTECTED]> writes: > I got compiletime errors: > In file included from /usr/include/kpathsea/kpathsea.h:27, > from kpath.cc:19: > /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 > make[1]: *** [out/kpath.o] Error 1 > make[1]: Leaving directory `/perl/stuff/sound/lilybuild/lilypond-1.4.7/lily' > make: *** [all] Error 2 Ah' you're using cygwin > 1.3.2, there's a bug in the unistd.h/getopt headers. Try CPPFLAGS="-I$PREFIX/include -I$PREFIX/include/w32api -D__GETOPT_H__" \ ./configure --prefix=$PREFIX Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond build on cygwin stucks
"Gerrit P. Haase" <[EMAIL PROTECTED]> writes: > 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. Guile 1.5.2 will probably not work for lilypond-1.4. > But the problem with net_db.c and and_let*.scm are not adressed. Ah, these things are addressed in the cross packaging scripts. > I will try to send my patch so everyone on cygwin should succeed > to compile guile-1.4 without errors. Ok, that's fine. See my edits to the wiki. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond build on cygwin stucks
Jan Nieuwenhuizen schrieb am 2001-09-16, 11:52: >"Gerrit P. Haase" <[EMAIL PROTECTED]> 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 kpath.cc -o out/kpath.o >> In file included from /usr/include/kpathsea/kpathsea.h:27, >> from kpath.cc:19: >> /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. > >> lily-guile.cc: In function `class String ly_scm2string(scm_unused_struct *)': >> lily-guile.cc:187: 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. Gerrit -- =^..^= ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond build on cygwin stucks
"Gerrit P. Haase" <[EMAIL PROTECTED]> 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 kpath.cc -o out/kpath.o > In file included from /usr/include/kpathsea/kpathsea.h:27, > from kpath.cc:19: > /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. > lily-guile.cc: In function `class String ly_scm2string(scm_unused_struct *)': > lily-guile.cc:187: 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. 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. Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
lilypond build on cygwin stucks
Hello, 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 kpath.cc -o out/kpath.o In file included from /usr/include/kpathsea/kpathsea.h:27, from kpath.cc:19: /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 make[1]: *** [out/kpath.o] Error 1 make[1]: Leaving directory `/perl/stuff/sound/lilybuild/lilypond-1.4.7/lily' make: *** [all] Error 2 I have TeX (tetex) installed, now I have two getopt.h included... Is it possible to exclude getopt.h from kpathsea.h, or should I do s.th. cleverer? lily-guile.cc: In function `class String ly_scm2string(scm_unused_struct *)': lily-guile.cc:187: 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 Is this error following from the exclusion of getopt.h from kpathsea.h, or is it s.th. different which is wrong with my envionment? Gerrit -- =^..^= ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
