> checking for mgd_connect in -lmidgard... no
> *** You need the Midgard library for using mod_midgard. ***
> *** Use the --with-midgard option to tell ***
> *** the configure script where to look for the library. ***
> *** Check also that both the Midgard library and the MySQL ***
> *** client library are on your dynamic library load path. ***
> configure: error: Midgard library libmidgard not found
config.log will have more details on the problem.
> some other information:
>
> [root@dark mod_midgard-1.4beta4]# ldconfig -v|grep midgard
> /opt/midgard/lib:
> libmidgard.so.3 => libmidgard.so.3.1.0
>
> [root@dark mod_midgard-1.4beta4]# ldconfig -v|grep mysql
> libmysqlclient.so.6 => libmysqlclient.so.6.0.0
> libmysqlclient.so.6 => libmysqlclient.so.6.0.0
>
> our configure command:
> ./configure --with-apache=/opt/apache --with-midgard=/opt/midgard
The .so libs are only found by ld.so at run time. At compile time, gcc/ld
need help to find them. Here's what I do:
export LDFLAGS="-L/usr/lib/mysql -L/usr/local/lib -lmysqlclient -lcrypt"
export LIBS=$LDFLAGS
export LIB=$LDFLAGS
export PATH=$PATH:/usr/sbin
Adapt paths to your situation of course.
There's a bug in configure.in (now fixed in CVS) that makes --with-midgard
not work as intended. Open configure and search for withwal, change into
withval. This may be all that's needed to fix your problem.
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]
