Peter Gilles wrote:
>
> I've read nearly all messages on the midgard-list
> concerning this problem, and tried also all proposed
> solutions, but ./configure still can't find libmidgard
> (which is neatly compiled in /usr/local/lib/) nor
> libmysql (which is in /usr/local/mysql/lib and in
> /usr/local/lib; as *.so an *.a). All these paths are
> in my /etc/ld.so.conf, too. I'am using Linux, SuSE
> 6.2,egcs-1.1.2.
There's a lot of confusion on this matter it seems.
There are two entities when it comes to dynamically linked
libraries/binaries: the linker (ld) and the dynamic loader (ld.so)
When linking a dynamic library or executable the linker
records information in the object about what libraries the
dynamic loader will need when it is accessed, but the linker
doesn't use ld.so.conf.
The linker will by default only look in the 'traditional'
library directories /lib and /usr/lib and possibly /usr/local/lib,
depending on your compiler, but you'll need to supply some hints
to ld about where to find other libs.
Try:
LDFLAGS="-L/usr/lib/mysql" ./configure ....
or
LDFLAGS="-L/usr/lib/mysql -L/usr/local/lib" ./configure ....
if the first doesn't work.
If this does not solve your problem I'd like to see the last 20
or so lines of your config.log
Bye,
Emile
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
