Sebastien Hould wrote:
1. What does
ldd /usr/cyrus/bin/imapd (or wherever your imapd is)
show?
libsasl2.so.2 => /usr/local/lib/libsasl2.so.2 (0x40017000) libdl.so.2 => /lib/libdl.so.2 (0x40039000) libresolv.so.2 => /lib/libresolv.so.2 (0x4003c000) libdb-4.0.so => /lib/libdb-4.0.so (0x4004e000) libwrap.so.0 => /usr/lib/libwrap.so.0 (0x400f6000) libnsl.so.1 => /lib/libnsl.so.1 (0x40100000) libc.so.6 => /lib/tls/libc.so.6 (0x42000000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) libpthread.so.0 => /lib/tls/libpthread.so.0 (0x40115000)
Definitely linked against the wrong libdb. I had this problem once before but I thought once I specified the correct path to BerkeleyDB my problem went away. Try the following 3 configure options when compiling imapd:
--with-bdb=/usr/local/BerkeleyDB.4.2 \ --with-bdb-libdir=/usr/local/BerkeleyDB.4.2/lib \ --with-bdb-incdir=/usr/local/BerkeleyDB.4.2/include
If that doesn't work you can also try moving /usr/include/db.h to /usr/include/db.h.OLD when configuring/compiling imapd. That way you can be sure imapd is not trying to compile against /usr/include instead of /usr/local/BerkeleyDB.4.2
2. What configure options did you use to compile cyrus-sasl and cyrus-imapd?
For sasl :
--with-bdb-libdir=/usr/local/BerkeleyDB.4.2/lib \ --with-bdb-incdir=/usr/local/BerkeleyDB.4.2/include \ --disable-krb4 --enable-plain --with-dbpath=/etc/sasldb2
and for imapd (among other options):
--with-auth=unix
(I had tried previously with --with-bdb-libdir=/usr/local/BerkeleyDB.4.2/lib \ --with-bdb-incdir=/usr/local/BerkeleyDB.4.2/include
yet I had the same results)
Thanks Patrick
--- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
