Re: building v2.19.83 - can't find libguile.so.17
On Sun 26 Jan 2020 at 10:02:49 (-0500), Bric wrote: > > > > > > > > > Could you please set your mailer to send a text representation of your emails as well as this HTML? I know it's possible to do that in Open-Xchange Mailer as there is at least one contributor here who does so. Cheers, David.
Re: building v2.19.83 - can't find libguile.so.17
On January 26, 2020 at 10:02 AM Bric wrote: On January 25, 2020 at 4:21 AM David Kastrup < d...@gnu.org> wrote: Jonas Hahnfeld < hah...@hahnjo.de> writes: Am Freitag, den 24.01.2020, 16:45 -0500 schrieb Bric: i am building lilypond-2.19.83 on Ubuntu 18.04.2 LTS -pthread -L/usr/local/lib -lguile -lltdl -lgmp -lcrypt -lm -lltdl how can i make lilypond find the shared object? I just checked and Ubuntu apparently doesn't look for libraries in /usr/local/lib (at least on my system). If you want it to, you might try export'ing LD_LIBRARY_PATH=/usr/local/lib in your shell. This *should* work without removing other versions of guile from your system. I have my version of Guile-1.8 installed in a place where Ubuntu will most certainly not bother looking unless told otherwise guile-config is supposed to be supplying the required options for compiling and linking to make it look in the installation place relevant when guile-config was being installed. Well, i don't know what happened at this point. I got a minute to get back to it just now, ran "make" in the source root, where I was getting the error earlier, and make finished ! Then "sudo make install" and "lilypond --version" is now showing "...2.19.83" i don't remember what i may have done a couple of days ago - with library paths or guile-config, etc. Sorry. This successful build still has the ./configure options I sent a few days ago: $ ./configure GUILE=/usr/bin/guile GUILE_CONFIG=/usr/local/bin/guile-config and to answer the question about LD_LIBRARY_PATH : mine is/was empty; i did not set it to /usr/local/lib I just remembered: I ran ./smart-autogen.sh in the source root earlier - that may have fixed it (?) I don't remember if I also ran ./smart-configure.sh -- David Kastrup
Re: building v2.19.83 - can't find libguile.so.17
On January 25, 2020 at 4:21 AM David Kastrup < d...@gnu.org> wrote: Jonas Hahnfeld < hah...@hahnjo.de> writes: Am Freitag, den 24.01.2020, 16:45 -0500 schrieb Bric: i am building lilypond-2.19.83 on Ubuntu 18.04.2 LTS -pthread -L/usr/local/lib -lguile -lltdl -lgmp -lcrypt -lm -lltdl how can i make lilypond find the shared object? I just checked and Ubuntu apparently doesn't look for libraries in /usr/local/lib (at least on my system). If you want it to, you might try export'ing LD_LIBRARY_PATH=/usr/local/lib in your shell. This *should* work without removing other versions of guile from your system. I have my version of Guile-1.8 installed in a place where Ubuntu will most certainly not bother looking unless told otherwise guile-config is supposed to be supplying the required options for compiling and linking to make it look in the installation place relevant when guile-config was being installed. Well, i don't know what happened at this point. I got a minute to get back to it just now, ran "make" in the source root, where I was getting the error earlier, and make finished ! Then "sudo make install" and "lilypond --version" is now showing "...2.19.83" i don't remember what i may have done a couple of days ago - with library paths or guile-config, etc. Sorry. This successful build still has the ./configure options I sent a few days ago: $ ./configure GUILE=/usr/bin/guile GUILE_CONFIG=/usr/local/bin/guile-config and to answer the question about LD_LIBRARY_PATH : mine is/was empty; i did not set it to /usr/local/lib -- David Kastrup
Re: building v2.19.83 - can't find libguile.so.17
Jonas Hahnfeld writes:
> Am Samstag, den 25.01.2020, 10:37 +0100 schrieb David Kastrup:
>> Jonas Hahnfeld <
>> hah...@hahnjo.de
>> > writes:
>>
>> > Am Samstag, den 25.01.2020, 10:21 +0100 schrieb David Kastrup:
>> > > Jonas Hahnfeld <
>> > > hah...@hahnjo.de
>> > >
>> > > > writes:
>> > > > Am Freitag, den 24.01.2020, 16:45 -0500 schrieb Bric:
>> > > > > i am building lilypond-2.19.83 on Ubuntu 18.04.2 LTS
>> > > > >
>> > > > >
>> > > > > -pthread -L/usr/local/lib -lguile -lltdl -lgmp -lcrypt -lm -lltdl
>> > > > >
>> > > > >
>> > > > > how can i make lilypond find the shared object?
>> > > >
>> > > > I just checked and Ubuntu apparently doesn't look for libraries in
>> > > > /usr/local/lib (at least on my system). If you want it to, you might
>> > > > try export'ing LD_LIBRARY_PATH=/usr/local/lib in your shell. This
>> > > > *should* work without removing other versions of guile from your
>> > > > system.
>> > >
>> > > I have my version of Guile-1.8 installed in a place where Ubuntu will
>> > > most certainly not bother looking unless told otherwise
>> > >
>> > > guile-config is supposed to be supplying the required options for
>> > > compiling and linking to make it look in the installation place relevant
>> > > when guile-config was being installed.
>> >
>> > The error message is not about linking, but happens during runtime.
>>
>> But during linking the place to look for a library at runtime can be
>> embedded into the executable.
>>
>> dak@lola:/usr/local/tmp/lilypond$ ldd `which lilypond`
>> linux-vdso.so.1 (0x7ffd3b853000)
>> libguile.so.17 => /usr/local/tmp/guile-1.8/lib/libguile.so.17
>> (0x7f60c85d8000)
>> [...]
>>
>> dak@lola:/usr/local/tmp/lilypond$ grep guile /etc/ld.so.conf.d/*
>> /etc/ld.so.conf.d/x86_64-linux-gnu_guile-1.8.conf:/usr/local/tmp/guile-1.8/lib
>>
>> Oh. I did not put this manually there, so it likely ended up there with
>>
>> sudo make install
>>
>> dak@lola:/usr/local/tmp/lilypond$ ls -l
>> /etc/ld.so.conf.d/x86_64-linux-gnu_guile-1.8.conf
>> -rw-r--r-- 1 root root 29 Aug 2 2017
>> /etc/ld.so.conf.d/x86_64-linux-gnu_guile-1.8.conf
>
> I don't see anything in guile-1.8.8 that would so. Libtool suggests it
> as one possibility, but I don't think it'll do so automatically.
>
> Anyway, I think that goes beyond the scope of the initial issue. The
> solution is to make the system find your dynamic libraries, with
> whatever method your prefer.
Maybe it got there via pkgconfig? There is
dak@lola:/usr/local/tmp/guile$ git grep pkgconfig
ChangeLog-2008: (pkgconfigdir, pkgconfig_DATA): New.
Makefile.am:pkgconfigdir = $(libdir)/pkgconfig
Makefile.am:pkgconfig_DATA = guile-1.8.pc
doc/ref/autoconf.texi:@file{@var{prefix}/lib/pkgconfig/guile-1.8.pc}, which
contains all the
and
dak@lola:/usr/local/tmp/guile$ locate guile-1.8.pc
/usr/local/tmp/guile/guile-1.8.pc
/usr/local/tmp/guile/guile-1.8.pc.in
/usr/local/tmp/guile-1.8/lib/pkgconfig/guile-1.8.pc
Not sure that means anything.
--
David Kastrup
Re: building v2.19.83 - can't find libguile.so.17
Am Samstag, den 25.01.2020, 10:37 +0100 schrieb David Kastrup: > Jonas Hahnfeld < > hah...@hahnjo.de > > writes: > > > Am Samstag, den 25.01.2020, 10:21 +0100 schrieb David Kastrup: > > > Jonas Hahnfeld < > > > hah...@hahnjo.de > > > > > > > writes: > > > > Am Freitag, den 24.01.2020, 16:45 -0500 schrieb Bric: > > > > > i am building lilypond-2.19.83 on Ubuntu 18.04.2 LTS > > > > > > > > > > > > > > > -pthread -L/usr/local/lib -lguile -lltdl -lgmp -lcrypt -lm -lltdl > > > > > > > > > > > > > > > how can i make lilypond find the shared object? > > > > > > > > I just checked and Ubuntu apparently doesn't look for libraries in > > > > /usr/local/lib (at least on my system). If you want it to, you might > > > > try export'ing LD_LIBRARY_PATH=/usr/local/lib in your shell. This > > > > *should* work without removing other versions of guile from your > > > > system. > > > > > > I have my version of Guile-1.8 installed in a place where Ubuntu will > > > most certainly not bother looking unless told otherwise > > > > > > guile-config is supposed to be supplying the required options for > > > compiling and linking to make it look in the installation place relevant > > > when guile-config was being installed. > > > > The error message is not about linking, but happens during runtime. > > But during linking the place to look for a library at runtime can be > embedded into the executable. > > dak@lola:/usr/local/tmp/lilypond$ ldd `which lilypond` > linux-vdso.so.1 (0x7ffd3b853000) > libguile.so.17 => /usr/local/tmp/guile-1.8/lib/libguile.so.17 > (0x7f60c85d8000) > [...] > > dak@lola:/usr/local/tmp/lilypond$ grep guile /etc/ld.so.conf.d/* > /etc/ld.so.conf.d/x86_64-linux-gnu_guile-1.8.conf:/usr/local/tmp/guile-1.8/lib > > Oh. I did not put this manually there, so it likely ended up there with > > sudo make install > > dak@lola:/usr/local/tmp/lilypond$ ls -l > /etc/ld.so.conf.d/x86_64-linux-gnu_guile-1.8.conf > -rw-r--r-- 1 root root 29 Aug 2 2017 > /etc/ld.so.conf.d/x86_64-linux-gnu_guile-1.8.conf I don't see anything in guile-1.8.8 that would so. Libtool suggests it as one possibility, but I don't think it'll do so automatically. Anyway, I think that goes beyond the scope of the initial issue. The solution is to make the system find your dynamic libraries, with whatever method your prefer. Jonas signature.asc Description: This is a digitally signed message part
Re: building v2.19.83 - can't find libguile.so.17
Jonas Hahnfeld writes: > Am Samstag, den 25.01.2020, 10:21 +0100 schrieb David Kastrup: >> Jonas Hahnfeld < >> hah...@hahnjo.de >> > writes: >> >> > Am Freitag, den 24.01.2020, 16:45 -0500 schrieb Bric: >> > > i am building lilypond-2.19.83 on Ubuntu 18.04.2 LTS >> > > >> > > >> > > -pthread -L/usr/local/lib -lguile -lltdl -lgmp -lcrypt -lm -lltdl >> > > >> > > >> > > how can i make lilypond find the shared object? >> > >> > I just checked and Ubuntu apparently doesn't look for libraries in >> > /usr/local/lib (at least on my system). If you want it to, you might >> > try export'ing LD_LIBRARY_PATH=/usr/local/lib in your shell. This >> > *should* work without removing other versions of guile from your >> > system. >> >> I have my version of Guile-1.8 installed in a place where Ubuntu will >> most certainly not bother looking unless told otherwise >> >> guile-config is supposed to be supplying the required options for >> compiling and linking to make it look in the installation place relevant >> when guile-config was being installed. > > The error message is not about linking, but happens during runtime. But during linking the place to look for a library at runtime can be embedded into the executable. dak@lola:/usr/local/tmp/lilypond$ ldd `which lilypond` linux-vdso.so.1 (0x7ffd3b853000) libguile.so.17 => /usr/local/tmp/guile-1.8/lib/libguile.so.17 (0x7f60c85d8000) [...] dak@lola:/usr/local/tmp/lilypond$ grep guile /etc/ld.so.conf.d/* /etc/ld.so.conf.d/x86_64-linux-gnu_guile-1.8.conf:/usr/local/tmp/guile-1.8/lib Oh. I did not put this manually there, so it likely ended up there with sudo make install dak@lola:/usr/local/tmp/lilypond$ ls -l /etc/ld.so.conf.d/x86_64-linux-gnu_guile-1.8.conf -rw-r--r-- 1 root root 29 Aug 2 2017 /etc/ld.so.conf.d/x86_64-linux-gnu_guile-1.8.conf And some time ago it seems. dak@lola:/usr/local/tmp/lilypond$ ls -l /usr/local/tmp/guile-1.8/bin/guile-config -rwxr-xr-x 1 root root 9136 Aug 14 2018 /usr/local/tmp/guile-1.8/bin/guile-config That one has been updated more recently. > There are ways to make the linker add a library path for runtime > (rpath), but it doesn't seem to kick in here. I had the same problem > with Ubuntu the other day when I was testing my changes for Python 3. > That's why I recommend using LD_LIBRARY_PATH instead of removing all > other versions of Guile. LD_LIBRARY_PATH is empty on my system. > > It it works for you, then I guess there is some setup somewhere, either > LD_LIBRARY_PATH or a change in /etc/ld.so.conf or ... Just do an `ldd' > on your executable and if the library is not in /usr/lib/ then > something non-standard is going on. > > Jonas -- David Kastrup
Re: building v2.19.83 - can't find libguile.so.17
Am Samstag, den 25.01.2020, 10:21 +0100 schrieb David Kastrup: > Jonas Hahnfeld < > hah...@hahnjo.de > > writes: > > > Am Freitag, den 24.01.2020, 16:45 -0500 schrieb Bric: > > > i am building lilypond-2.19.83 on Ubuntu 18.04.2 LTS > > > > > > > > > -pthread -L/usr/local/lib -lguile -lltdl -lgmp -lcrypt -lm -lltdl > > > > > > > > > how can i make lilypond find the shared object? > > > > I just checked and Ubuntu apparently doesn't look for libraries in > > /usr/local/lib (at least on my system). If you want it to, you might > > try export'ing LD_LIBRARY_PATH=/usr/local/lib in your shell. This > > *should* work without removing other versions of guile from your > > system. > > I have my version of Guile-1.8 installed in a place where Ubuntu will > most certainly not bother looking unless told otherwise > > guile-config is supposed to be supplying the required options for > compiling and linking to make it look in the installation place relevant > when guile-config was being installed. The error message is not about linking, but happens during runtime. There are ways to make the linker add a library path for runtime (rpath), but it doesn't seem to kick in here. I had the same problem with Ubuntu the other day when I was testing my changes for Python 3. That's why I recommend using LD_LIBRARY_PATH instead of removing all other versions of Guile. It it works for you, then I guess there is some setup somewhere, either LD_LIBRARY_PATH or a change in /etc/ld.so.conf or ... Just do an `ldd' on your executable and if the library is not in /usr/lib/ then something non-standard is going on. Jonas signature.asc Description: This is a digitally signed message part
Re: building v2.19.83 - can't find libguile.so.17
Jonas Hahnfeld writes: > Am Freitag, den 24.01.2020, 16:45 -0500 schrieb Bric: >> i am building lilypond-2.19.83 on Ubuntu 18.04.2 LTS >> >> >> -pthread -L/usr/local/lib -lguile -lltdl -lgmp -lcrypt -lm -lltdl >> >> >> how can i make lilypond find the shared object? > > I just checked and Ubuntu apparently doesn't look for libraries in > /usr/local/lib (at least on my system). If you want it to, you might > try export'ing LD_LIBRARY_PATH=/usr/local/lib in your shell. This > *should* work without removing other versions of guile from your > system. I have my version of Guile-1.8 installed in a place where Ubuntu will most certainly not bother looking unless told otherwise guile-config is supposed to be supplying the required options for compiling and linking to make it look in the installation place relevant when guile-config was being installed. -- David Kastrup
Re: building v2.19.83 - can't find libguile.so.17
Am Freitag, den 24.01.2020, 16:45 -0500 schrieb Bric: > i am building lilypond-2.19.83 on Ubuntu 18.04.2 LTS > > > > had to build guile-1.8.8, after which lilypond ./configure was happy, and > finished (posted about my guile struggles a few days ago) > > > > But "make" errors out with: > > > > cat Documentation/out/generate-documentation.log : > > > > /lilypond-2.19.83/out/bin/lilypond: error while loading shared > libraries: libguile.so.17: cannot open shared object file: No such file or > directory > > > i built guile to /usr/local/lib, and have a symlink with the above file name > lilypond can't find > > > > ls -l /usr/local/lib/libguile.so.17* > > > > lrwxrwxrwx 1 root root 18 Jan 18 23:54 /usr/local/lib/libguile.so.17 -> > libguile.so.17.4.0 > -rwxr-xr-x 1 root root 4607496 Jan 18 23:54 /usr/local/lib/libguile.so.17.4.0 > > > guile-config link : > > > > -pthread -L/usr/local/lib -lguile -lltdl -lgmp -lcrypt -lm -lltdl > > > how can i make lilypond find the shared object? I just checked and Ubuntu apparently doesn't look for libraries in /usr/local/lib (at least on my system). If you want it to, you might try export'ing LD_LIBRARY_PATH=/usr/local/lib in your shell. This *should* work without removing other versions of guile from your system. Jonas signature.asc Description: This is a digitally signed message part
Re: building v2.19.83 - can't find libguile.so.17
Am Fr., 24. Jan. 2020 um 22:51 Uhr schrieb David Kastrup : > > Bric writes: > > > i am building lilypond-2.19.83 on Ubuntu 18.04.2 LTS > > > > had to build guile-1.8.8, after which lilypond ./configure was happy, and > > finished (posted > > about my guile struggles a few days ago) > > > > But "make" errors out with: > > > > cat Documentation/out/generate-documentation.log : > > > > /lilypond-2.19.83/out/bin/lilypond: error while loading shared > > libraries: > > libguile.so.17: cannot open shared object file: No such file or directory > > > > i built guile to /usr/local/lib, and have a symlink with the above file > > name lilypond can't find > > > > ls -l /usr/local/lib/libguile.so.17* > > > > lrwxrwxrwx 1 root root 18 Jan 18 23:54 /usr/local/lib/libguile.so.17 -> > > libguile.so.17.4.0 > > -rwxr-xr-x 1 root root 4607496 Jan 18 23:54 > > /usr/local/lib/libguile.so.17.4.0 > > > > guile-config link : > > > > -pthread -L/usr/local/lib -lguile -lltdl -lgmp -lcrypt -lm -lltdl > > > > how can i make lilypond find the shared object? > > I use > > ./configure GUILE=/usr/bin/guile > GUILE_CONFIG=/usr/local/tmp/guile-1.8/bin/guile-config Bric, do you have other guile-versions around? I made the experience that sometimes configure picks wrongly then, although the double-checked pathes were ok. In this case easiest may be to throw away other guiles and restart. Or, sometimes I succeeded running ldconfig after ´sudo make install´ Cheers, Harm > > and that's basically all. GUILE can be a 2.x Guile version (it is used > for scripting), but GUILE_CONFIG needs to be the 1.8 build. > > -- > David Kastrup >
Re: building v2.19.83 - can't find libguile.so.17
Bric writes: > On January 24, 2020 at 4:50 PM David Kastrup < d...@gnu.org> wrote: > > Bric < b...@flight.us> writes: > > i am building lilypond-2.19.83 on Ubuntu 18.04.2 LTS > > had to build guile-1.8.8, after which lilypond ./configure was happy, and > finished > (posted > about my guile struggles a few days ago) > > -pthread -L/usr/local/lib -lguile -lltdl -lgmp -lcrypt -lm -lltdl > > how can i make lilypond find the shared object? > > I use > > ./configure GUILE=/usr/bin/guile > GUILE_CONFIG=/usr/local/tmp/guile-1.8/bin/guile-config > > and that's basically all. GUILE can be a 2.x Guile version (it is used > for scripting), but GUILE_CONFIG needs to be the 1.8 build. > > I tried your method and got the same error. Can't find libguile.so.17 Then likely building and installing guile did not complete. -- David Kastrup
Re: building v2.19.83 - can't find libguile.so.17
On January 24, 2020 at 4:50 PM David Kastrup <
d...@gnu.org> wrote:
Bric <
b...@flight.us> writes:
i am building lilypond-2.19.83 on Ubuntu 18.04.2 LTS
had to build guile-1.8.8, after which lilypond ./configure was happy, and finished (posted
about my guile struggles a few days ago)
-pthread -L/usr/local/lib -lguile -lltdl -lgmp -lcrypt -lm -lltdl
how can i make lilypond find the shared object?
I use
./configure GUILE=/usr/bin/guile GUILE_CONFIG=/usr/local/tmp/guile-1.8/bin/guile-config
and that's basically all. GUILE can be a 2.x Guile version (it is used
for scripting), but GUILE_CONFIG needs to be the 1.8 build.
I tried your method and got the same error. Can't find libguile.so.17
attaching the config.log of this latest attempt
--
David Kastrup
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by configure, which was
generated by GNU Autoconf 2.69. Invocation command line was
$ ./configure GUILE=/usr/bin/guile GUILE_CONFIG=/usr/local/bin/guile-config
## - ##
## Platform. ##
## - ##
hostname = li742-122
uname -m = x86_64
uname -r = 4.15.0-45-generic
uname -s = Linux
uname -v = #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019
/usr/bin/uname -p = unknown
/bin/uname -X = unknown
/bin/arch = unknown
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
PATH: /home//.local/bin
PATH: /usr/local/sbin
PATH: /usr/local/bin
PATH: /usr/sbin
PATH: /usr/bin
PATH: /sbin
PATH: /bin
PATH: /usr/games
PATH: /usr/local/games
PATH: /snap/bin
PATH: /usr/local/lib
## --- ##
## Core tests. ##
## --- ##
configure:2338: checking build system type
configure:2352: result: x86_64-unknown-linux-gnu
configure:2372: checking host system type
configure:2385: result: x86_64-unknown-linux-gnu
configure:2439: checking Package
configure:2464: result: LILYPOND
configure:2467: checking builddir
configure:2479: result: /data/installers/lily/lilypond-2.19.83
configure:2482: checking for stepmake
configure:2490: result: ./stepmake (${datarootdir}/stepmake not found)
configure:2564: checking for gmake
configure:2594: result: no
configure:2564: checking for make
configure:2580: found /usr/bin/make
configure:2591: result: make
configure:2714: checking for find
configure:2730: found /usr/bin/find
configure:2741: result: find
configure:2865: checking for tar
configure:2881: found /bin/tar
configure:2892: result: tar
configure:3145: checking for bash
configure:3176: result: /bin/bash
configure:3188: checking for python
configure:3276: result: python
configure:3279: checking python version
configure:3281: result: 2.7.17
configure:3291: checking for python
configure:3309: found /usr/bin/python
configure:3321: result: /usr/bin/python
configure:3482: checking how to replicate source files to build files
configure:3490: result: ln
configure:3607: checking for gcc
configure:3623: found /usr/local/bin/gcc
configure:3634: result: gcc
configure:3863: checking for C compiler version
configure:3872: gcc --version >&5
gcc (GCC) 9.2.0
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
configure:3883: $? = 0
configure:3872: gcc -v >&5
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/x86_64-pc-linux-gnu/9.2.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../configure --disable-multilib
Thread model: posix
gcc version 9.2.0 (GCC)
configure:3883: $? = 0
configure:3872: gcc -V >&5
gcc: error: unrecognized command line option '-V'
gcc: fatal error: no input files
compilation terminated.
configure:3883: $? = 1
configure:3872: gcc -qversion >&5
gcc: error: unrecognized command line option '-qversion'; did you mean '--version'?
gcc: fatal error: no input files
compilation terminated.
configure:3883: $? = 1
configure:3903: checking whether the C compiler works
configure:3925: gccconftest.c >&5
conftest.c:9: warning: "PACKAGE_NAME" redefined
9 | #define PACKAGE_NAME "LilyPond"
|
conftest.c:2: note: this is the location of the previous definition
2 | #define PACKAGE_NAME ""
|
configure:3929: $? = 0
configure:3977: result: yes
configure:3980: checking for C compiler default output file name
configure:3982: result: a.out
configure:3988: checking for suffix of executables
configure:3995: gcc -o
Re: building v2.19.83 - can't find libguile.so.17
Bric writes: > i am building lilypond-2.19.83 on Ubuntu 18.04.2 LTS > > had to build guile-1.8.8, after which lilypond ./configure was happy, and > finished (posted > about my guile struggles a few days ago) > > But "make" errors out with: > > cat Documentation/out/generate-documentation.log : > > /lilypond-2.19.83/out/bin/lilypond: error while loading shared > libraries: > libguile.so.17: cannot open shared object file: No such file or directory > > i built guile to /usr/local/lib, and have a symlink with the above file name > lilypond can't find > > ls -l /usr/local/lib/libguile.so.17* > > lrwxrwxrwx 1 root root 18 Jan 18 23:54 /usr/local/lib/libguile.so.17 -> > libguile.so.17.4.0 > -rwxr-xr-x 1 root root 4607496 Jan 18 23:54 /usr/local/lib/libguile.so.17.4.0 > > guile-config link : > > -pthread -L/usr/local/lib -lguile -lltdl -lgmp -lcrypt -lm -lltdl > > how can i make lilypond find the shared object? I use ./configure GUILE=/usr/bin/guile GUILE_CONFIG=/usr/local/tmp/guile-1.8/bin/guile-config and that's basically all. GUILE can be a 2.x Guile version (it is used for scripting), but GUILE_CONFIG needs to be the 1.8 build. -- David Kastrup
building v2.19.83 - can't find libguile.so.17
i am building lilypond-2.19.83 on Ubuntu 18.04.2 LTS had to build guile-1.8.8, after which lilypond ./configure was happy, and finished (posted about my guile struggles a few days ago) But "make" errors out with: cat Documentation/out/generate-documentation.log : /lilypond-2.19.83/out/bin/lilypond: error while loading shared libraries: libguile.so.17: cannot open shared object file: No such file or directory i built guile to /usr/local/lib, and have a symlink with the above file name lilypond can't find ls -l /usr/local/lib/libguile.so.17* lrwxrwxrwx 1 root root 18 Jan 18 23:54 /usr/local/lib/libguile.so.17 -> libguile.so.17.4.0 -rwxr-xr-x 1 root root 4607496 Jan 18 23:54 /usr/local/lib/libguile.so.17.4.0 guile-config link : -pthread -L/usr/local/lib -lguile -lltdl -lgmp -lcrypt -lm -lltdl how can i make lilypond find the shared object?
