Il giorno ven 20 ott 2017 alle 21:52, David Kastrup <[email protected]> ha
scritto:
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.
Ok, I thought that it was not necessary as I have now, after removing
guile-2, only one guile-config in my PATH.
I found out that there's another requirement needed: running ldconfig
after guile-1.8 installation.
For the records, these are the commands that worked well to build and
install guile-1.8 system wide on debian stretch:
git clone https://git.savannah.gnu.org/git/guile.git
cd guile
git checkout branch_release-1-8
./autogen.sh
./configure --disable-error-on-warning --prefix=/usr/local
make
sudo make install
sudo ldconfig
echo "GUILE_CONFIG=/usr/local/bin/guile-config" >> ~/.bashrc
_______________________________________________
lilypond-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
