Am Samstag, den 25.01.2020, 10:21 +0100 schrieb David Kastrup: > Jonas Hahnfeld < > [email protected] > > 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
