>>>>> On Thu, 21 Mar 2002 16:26:33 +0100, >>>>> Birger Toedtmann <[EMAIL PROTECTED]> (bt) writes:
bt> The problem mostly lies with the header files. I had the same effect bt> once. I had installed BDB3 and 4 on one machine, and the db header file bt> (include/db.h) pointed towards BDB3 whereas the linker itself grabbed bt> /lib/libdb-4.so. at the end of the compile. Just be sure that db.h bt> points to the BDB version you're going to link in (I did it with a soft- bt> link to include/db4/db.h). It is for this reason that when I install BDB on our Solaris systems I no longer attempt to link everything into /usr/local/include and /usr/local/lib. I think there is a reason why Sleepycat by default wants to put these headers/libraries into an application-specific directory. Yes that makes compiling a bit more involved, but it also avoid all these double link problems that folks go on about. It also means I have no problems with BDB-3.x and BDB-4.x both being installed on the same system. No collisions. To some extent I think it was a mistake of Redhat to try to defeat the version-specific directories that Sleepycat does by default..... Been there, done that.... -- Amos
