From dev-return-5063-apmail-apr-dev-archive=apr.apache.org@apr.apache.org Wed Dec 05 17:04:48 2001 Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 44393 invoked by uid 500); 5 Dec 2001 17:04:47 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 44373 invoked from network); 5 Dec 2001 17:04:46 -0000 From: blaiset@cnet.com (Blaise Tarr) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15374.21402.379144.899591@cnet.com> Date: Wed, 5 Dec 2001 12:04:26 -0500 To: dev@apr.apache.org Subject: Re: [PATCH] Improved Berkeley DB detection In-Reply-To: <20011205033359.GD22835@ebuilt.com> References: <20011205033359.GD22835@ebuilt.com> X-Mailer: VM 6.95 under 21.1 (patch 3) "Acadia" XEmacs Lucid X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Justin Erenkrantz writes: > Highlights: > > - Split out DB2 and DB3 detection since they are no longer related > (as DB3 only has db_create and DB2 has db_open). Was db_open in > any released version of DB3? AFAIK, 3.0.55 was the first released DB3, and it didn't have db_open. > - Check for db[23]/db.h and db[23] to be nicer about detecting > platforms that have this combination. > > And, this removes my entry in STATUS about --with-dbm=db2 not > working correctly when db3 is available. > > Thoughts? > > Per previous conversation, should we remove db185? +1 Incidentally, Berkeley DB 4.0.14 is now available. > -- justin Blaise