On Wed, 27 Jan 1999, Mats Bengtsson wrote:
> I guess it also depends on how your Guile is configured.
> If it is configured to use qthreads, than I don't think
> that Lilypond's configuration script will detect Guile
> correctly.
Well, I didn't configure guile with qthreads, and lily's configure
still doesn't recognize it, nor does it find readline.
If you'd like to have a look at it, here's how I configured guile:
../configure i686-pc-linux-gnu --with-gnu-as --with-gnu-ld
--exec-prefix=/usr/i686-linux-libc6
--includedir=/usr/i686-linux-libc6/include --enable-shared
--enable-dynamic-linking
The unusual prefices come from my glibc-installation, which lives
in /usr/i686-linux-libc6 as I followed the installation instructions
of Frodo Looijaard (http://huizen.dds.nl/~frodol/glibc/).
In a similar way I configured readline (no enable-options because the
shared library is there an additional make target), and guile's
configure script recognized it (since I compiled it afterwards).
My solution was first to link the .o files in lily explicitely with
-lguile and -lreadline, but that's ruther cumbersome.
Then I edited config.make and added -lguile and -lreadline to EXTRALIBES,
but it didn't work until I also added -ldl and -lncurses.
Anyway, if this leads to the correct results (a running lily), it should
be okay, shouldn't it?
Thanks for your help in advance
David
[EMAIL PROTECTED]
