When running ldconfig, it saves the information in the
/var/run/ld-elf.so.hints file, and I assume that ld should then know
where libraries are located, since they are in this cache file. So when
running: ld -lexpat, why did ld not know the location of the expat
library, when it is in the cache
- Original Message -
From: Justin Hopper [EMAIL PROTECTED]
To: Matthew Emmerton [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Saturday, January 04, 2003 5:35 AM
Subject: Re: Mysterious problem with ldconfig and ld
What ultimately fixed the problem was hardcoding the
-L /usr/local/lib
This may be a very simple fix, but so far I've found no solution. Just
installed expat-1.95.5 in a FreeBSD 4.4 machine. The install went fine,
and I verified that ldconfig had picked up the library:
host# ldconfig -r | grep expat
73:-lexpat.4 = /usr/local/lib/libexpat.so.4
However, I need to
This may be a very simple fix, but so far I've found no solution. Just
installed expat-1.95.5 in a FreeBSD 4.4 machine. The install went fine,
and I verified that ldconfig had picked up the library:
host# ldconfig -r | grep expat
73:-lexpat.4 = /usr/local/lib/libexpat.so.4
However, I
Hmmm, I guess I just assumed that since ldconfig had cached the absolute
path to the library, ld would not need to know the library path as well,
but for some reason it did.
What ultimately fixed the problem was hardcoding the -L /usr/local/lib
in the configure script, since it refused to pick up
In the last episode (Jan 03), Justin Hopper said:
Hmmm, I guess I just assumed that since ldconfig had cached the
absolute path to the library, ld would not need to know the library
path as well, but for some reason it did.
What ultimately fixed the problem was hardcoding the -L
