Lars Peterson wrote:

Snippet from configure's output:
<===
checking for db.h... yes
checking for db_create in -ldb-4.1... no
checking for db_create in -ldb4.1... no
checking for db_create in -ldb41... no
checking for db_create in -ldb-4.0... yes
===>

When I do an ldd on the resultant imapd binary after the build finishes, I see
that it been linked to the bdb libraries that came with the RedHat install
(4.0.14-20).

I've played around with LDFLAGS, CPPFLAGS, and LD_LIBRARY_PATH environment
variables to try and force the directories of my non-standard libraries and
headers to be loaded first, but that didn't change a thing.

I'm reluctant to remove the RedHat db4 installation because I quite certain that
it would break a large amount of dependencies...

Any ideas?


In the directory you passed for bdb-libdir, is there a libdb-4.1.so? Are permissions on it set properly?

BTW, you may be happier using 4.0.14. On Solaris anyway, I consistently ran into problems after a week or two of uptime with 4.1.25, and that all went away after downgrading to 4.0.14.

--
John A. Tamplin                               Unix System Administrator
Emory University, School of Public Health     +1 404/727-9931




Reply via email to