On Wednesday 10 October 2001 02:33, you wrote: > Hi Kohei, > > > Try > > > > cd /usr/lib > > ln -s /usr/local/BerkeleyDB.3.3/lib/libdb-3.3.so > > ln -s /usr/local/BerkeleyDB.3.3/lib/libdb-3.3.a > > Didn't have any effect on my system. > > - Did you have an signaled to death (11) as well?
No I didn't get that particular error message. I guess I was lucky. > > I would be nice to get your content of > - ldd master > - ldd imapd > and ldd libsasl.so Here you go. $ ldd master libdl.so.2 => /lib/libdl.so.2 (0x40024000) libdb-3.3.so => /usr/local/BerkeleyDB.3.3/lib/libdb-3.3.so (0x40028000) libresolv.so.2 => /lib/libresolv.so.2 (0x400a7000) libcom_err.so.2 => /lib/libcom_err.so.2 (0x400b7000) libc.so.6 => /lib/libc.so.6 (0x400bb000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) $ ldd imapd libsasl.so.7 => /usr/local/lib/libsasl.so.7 (0x40014000) libdl.so.2 => /lib/libdl.so.2 (0x4002f000) libdb-3.3.so => /usr/local/BerkeleyDB.3.3/lib/libdb-3.3.so (0x40033000) libresolv.so.2 => /lib/libresolv.so.2 (0x400b2000) libcom_err.so.2 => /lib/libcom_err.so.2 (0x400c3000) libnsl.so.1 => /lib/libnsl.so.1 (0x400c6000) libc.so.6 => /lib/libc.so.6 (0x400dd000) libcrypt.so.1 => /lib/libcrypt.so.1 (0x401c4000) libpam.so.0 => /lib/libpam.so.0 (0x401f1000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) $ ldd libsasl.so libdb-3.3.so => /usr/lib/libdb-3.3.so (0x4001c000) libdl.so.2 => /lib/libdl.so.2 (0x4009b000) libcrypt.so.1 => /lib/libcrypt.so.1 (0x4009f000) libpam.so.0 => /lib/libpam.so.0 (0x400cc000) libresolv.so.2 => /lib/libresolv.so.2 (0x400d5000) libc.so.6 => /lib/libc.so.6 (0x400e5000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000) I see that your libsasl.so is linked against libdb.so.3, while mine is against libdb-3.3.so. > Did you do a recompilation of cyrus-sasl after the > ln -s /usr/local/BerkeleyDB.3.3/lib/libdb-3.3.so > > > ln -s /usr/local/BerkeleyDB.3.3/lib/libdb-3.3.a > > stuff??? I probably did. I'm saying 'probably' here because I did so many recompilations I can't remember at what point I made the above simlinks. :( Since my libsasl.so appears to be linked with /usr/lib/libdb-3.3.so, I probably compiled SASL AFTER I made the symlinks. > At the moment I still have a signaled by death. > > For instance: What is your libdb.so.3 linked against? > /lib/libdb-2.1.3.so*?? # ldd libdb.so.3 libc.so.6 => /lib/libc.so.6 (0x40024000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) > And which packages did you use to install tar.gz or rpm? I compiled BerkeleyDB, SASL, Cyrus IMAP all from their source (i.e. tar.gz. files). I didn't use any rpm files. Just for a curiosity, what do you get when you do "rpm -qa | grep db"? Do you have any db1, db2, db3 rpms (and their "devel" rpm) installed? Here is my output: # rpm -qa | grep db pwdb-0.61-4mdk gdbm-1.8.0-8mdk gdb-5.0-4mdk kdbg-1.1.4-7mdk grdb-0.2.4-ximian.1 pwdb-devel-0.61-4mdk gdbm-devel-1.8.0-8mdk xxgdb-1.12-18mdk If you have any of db[123] rpms installed, can you uninstall them without breaking dependencies? > Sorry, about all these question, but I feel a bit > embarassed about the non-working cyrus and > would do "high-jumping" and "lol's" when I would get it to > work.... Oh don't worry it took me four days to figure everything out. This is a tough beast to deal with. Kohei > > Regards > > Jochen Metzger
