On Thu, Feb 06, 2003 at 04:54:40PM +0100, Klaus Litfin wrote: ... > Is the configure-Script corrupt or did i make a mistake with the parameters? > > A second/third try was a combination of > > (BerkleyDB 4.0.14, cyrus-sasl-2.1.12, and cyrus-imapd-2.1.12) > > or with (BerkleyDB 4.1.25, cyrus-sasl-2.1.12, and cyrus-imapd-2.1.12). > > At this time the configure-Script does not stop, but did not recognize > the correct version of the database. > ... > checking for vprintf... (cached) yes > checking for db.h... (cached) yes > checking for db_create in -ldb-4.1... (cached) no > checking for db_create in -ldb4.1... (cached) no > checking for db_create in -ldb-4.0... (cached) no > checking for db_create in -ldb4.0... (cached) no ...
One suggestion is to rm -rf config.cache between configure runs. It seems that you are just getting the results of the first run each time as they are still cached. (the db changing to yes is a bit strange though) The other option to look at is using the following configure options --with-dbdir=DIR Berkeley DB files are in prefix DIR --with-bdb-libdir=DIR Berkeley DB lib files are in DIR --with-bdb-incdir=DIR Berkeley DB include files are in DIR Cheers, Patrick
