[Ecls-list] About the need for ldconfig/ld.so.conf
Robert Lehr
bozzio at the-lehrs.com
Fri Oct 31 09:00:22 UTC 2003
On Fri, Oct 31, 2003 at 04:38:59PM +0100, Juan Jose Garcia-Ripoll wrote:
> On Friday 31 October 2003 16:21, Robert Lehr wrote:
> > On Fri, Oct 31, 2003 at 09:17:37AM +0100, Julian St. wrote:
> > > You probably have to add /usr/local/lib/ecl to your shared library
> > > search path, so the runtime linker can find libecl.so. On FreeBSD this
> > > works with 'ldconfig -m /usr/local/lib/ecl'. There should perhaps be a
> > > script that does this after OS startup.
> >
> > After reading your email, I realized that I had forgotten to add
> > /usr/lib/ecl to my /etc/ld.so.conf. I was too tired to think this even
> > with ldconfig screaming at me every time I tested the RPM.
>
> There is no need to either update ld.so.conf or use ldconfig when installing
> ECL. If everything went ok, the executable is configured to find the library
> at ${prefix}/lib/ecl/, and this information is hardcoded via the flag --rpath
> which is passed to the linker. At least it should be this way, and it works
> on all systems I have tried it. Just do the following experiment (replace
> /home/juanjo/bin/ecl with your executable file):
> $ ldd /home/juanjo/bin/ecl
> libecl.so => /home/juanjo/lib/ecl//libecl.so
> libdl.so.1 => /usr/lib/libdl.so.1
> libm.so.1 => /usr/lib/libm.so.1
> libc.so.1 => /usr/lib/libc.so.1
> /usr/platform/SUNW,UltraSPARC-IIi-Engine/lib/libc_psr.so.1
That is true for /usr/bin/ecl. But not for my application that is
linked to libecl.so
bozzio$ ldd <my-binary-program-built-using-usr-bin-ecl-config>
libecl.so => not found
libdl.so.2 => /lib/libdl.so.2 (0x40024000)
libm.so.6 => /lib/i686/libm.so.6 (0x40027000)
libc.so.6 => /lib/i686/libc.so.6 (0x42000000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
--
Robert Lehr
bozzio at the-lehrs.com
More information about the ecl-devel
mailing list