2.0.1 configure script.

[Michael Beattie]

I've just subscribed, and am Currently pulling down an mbox of the
archives.... excuse me if this has been covered.

configure.ac is badly written w.r.t searching for Berkeley DB. Trace
follows:

+ BERKELEY_DB_DIR=yes
+ echo 'configure:3888: checking whether BerkeleyDB is desired'
+ echo -n 'checking whether BerkeleyDB is desired... '
+ test xyes = xno
+ echo 'configure:3897: result: yes'
+ echo yes
+ echo 'configure:3899: checking for BerkeleyDB location'
+ echo -n 'checking for BerkeleyDB location... '
+ test xyes = xyes
+ test -d /opt/BerkeleyDB.3.2
+ test -d /usr/local/BerkeleyDB.3.2
+ test -d /usr/BerkeleyDB.3.2
+ test -d /opt/BerkeleyDB.3.3
+ test -d /usr/local/BerkeleyDB.3.3
+ test -d /usr/BerkeleyDB.3.3
+ test -d /opt/BerkeleyDB.4.0
+ test -d /usr/local/BerkeleyDB.4.0
+ test -d /usr/BerkeleyDB.4.0
+ test xyes = xyes
+ test -d yes/include/db4
+ test -d yes/include/db3
+ test -d yes/include/db2
+ test -d yes/include/db
+ test x = x
+ test -d yes/db4
+ test -d yes/db3
+ test -d yes/db2
+ test -d yes/db
+ test x = x
+ echo 'configure:3935: error: Cannot find BerkeleyDB'
+ echo 'configure: error: Cannot find BerkeleyDB'
configure: error: Cannot find BerkeleyDB


Which causes it to fail in most cases.

Should I write the patch?

Mike.
-- 
Michael Beattie <address@hidden>