Re: building v2.19.83 - can't find libguile.so.17

[David Kastrup]

Jonas Hahnfeld <address@hidden> writes:

> Am Samstag, den 25.01.2020, 10:37 +0100 schrieb David Kastrup:
>> Jonas Hahnfeld <
>> address@hidden
>> > writes:
>> 
>> > Am Samstag, den 25.01.2020, 10:21 +0100 schrieb David Kastrup:
>> > > Jonas Hahnfeld <
>> > > address@hidden
>> > > 
>> > > > 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 (0x00007ffd3b853000)
>>      libguile.so.17 => /usr/local/tmp/guile-1.8/lib/libguile.so.17 
>> (0x00007f60c85d8000)
>> [...]
>> 
>> 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