Federico Bruni <[email protected]> writes: >>> I have my own Guile 1.8 libraries. I use something like >>> >>> GUILE_CONFIG=/usr/local/tmp/guile-1.8/bin/guile-config ./configure >>> ... >>> >>> I got the same problem. However, this appears to be because avoiding >>> the check for guile-config in this manner appears to _also_ disable >>> the >>> check (and any useful default) for Guile. So I have to do >>> >>> GUILE=/usr/bin/guile GUILE_CONFIG=... ./configure ... >>> >>> to get this working smoothly. /usr/bin/guile happens to be a >>> Guile-2.0 >>> provided by Ubuntu. It's fine since it is used for the scripts which >>> run ok under Guile-2.0. >>> >>> >> >> This did not help, unfortunately. I keep getting the same error. >> >> Now I've removed guile-2.0. >> I've built and installed guile-1.8 in /usr/local. /usr/local/bin is >> in my path. >> >> But I get this error: >> >> checking for guile-config... no
If your configure script is _checking_ for guile-config, you don't have GUILE_CONFIG set. -- David Kastrup _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
