From: Thimble Smith
Date: January 19 2001 11:59am
Subject: Re: MySQL 3.23.31 configure fails with Berkeley DB 3.2.3h
List-Archive: http://lists.mysql.com/mysql/62368
Message-Id: <20010119135936.D32602@cane.mysql.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

> >Description:
> 	I just downloaded MySQL 3.23.31 and the "patched version" of
> 	Berkeley DB 3.2.3h from the www.mysql.com site.  I ran configure
> 	with the option to enable the Berkeley DB, but it fails, telling
> 	me I don't have the proper version of the DB.  Here are the last
> 	few lines from the configure output:
> 
> 	checking for BerkeleyDB... supplied
> 	configure: error: didn't find valid BerkeleyDB: '/usr/local/BerkeleyDB.3.2' doesn't look like a BDB directory (invalid version 3.2.3 (must be at least version 3.2.3g))

Yes, this configure bug slipped through due to an international
conspiracy.  But the resistance is still powerful, as evidenced
by this patch:

--- acinclude.m4        Thu Jan 18 22:26:20 2001                                +++ /tmp/acinclude.m4   Fri Jan 19 13:58:24 2001
@@ -823,12 +823,12 @@
     bdb_version_ok=yes
   # This is ugly, but about as good as it can get
   elif test $db_major -eq 3 && test $db_minor -eq 2 && test $db_patch -eq 3 &&\
-       grep 'DB_VERSION_STRING.*g: ' [$1] > /dev/null
+       grep 'DB_VERSION_STRING.*h: ' [$1] > /dev/null
   then
     bdb_version_ok=yes
   else
     bdb_version_ok="invalid version $db_major.$db_minor.$db_patch"
-    bdb_version_ok="$bdb_version_ok (must be at least version 3.2.3g)"
+    bdb_version_ok="$bdb_version_ok (must be least version 3.2.3h)"
   fi
 ])
 

Sorry about that.

Tim

-- 
   __  ___     ___ ____  __
  /  |/  /_ __/ __/ __ \/ /    Tim Smith <tim@stripped>
 / /|_/ / // /\ \/ /_/ / /__   MySQL AB, Development Team
/_/  /_/\_, /___/\___\_\___/   Helsinki, Finland (for a few weeks)
       <___/   www.mysql.com