Bug 25340 - db4 check m4 rule
Summary: db4 check m4 rule
Status: RESOLVED WORKSFORME
Alias: None
Product: APR
Classification: Unclassified
Component: APR-util (show other bugs)
Version: HEAD
Hardware: Other other
: P3 normal (vote)
Target Milestone: ---
Assignee: Apache Portable Runtime bugs mailinglist
URL:
Keywords: PatchAvailable
Depends on:
Blocks:
 
Reported: 2003-12-08 21:02 UTC by VIkram Vijayaraghavan
Modified: 2004-11-16 19:05 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description VIkram Vijayaraghavan 2003-12-08 21:02:32 UTC
small change to the srclib/apr-util/build/apr-conf.m4 rule file. currently the
check for db4 goes like:
- check for db4
- check for db4.0

another check should be added to make it
- check for db4
- check for db-4
- check for db4.0

or at the very least it should be:
- check for db4
- check for db-4

this is because a libdb4 built from source usually defaults to libdb-4.so which
is a symlink to the actual version. we have encountered this more than once
while we built apache and lidb4 support from source.

the patch for [db4, db-4] . you might want to add back db-4.0 check in it. 
thanks for the great work!

---

diff -Naur source/httpd-2.0.47/srclib/apr-util/build/apu-conf.m4
build/httpd-2.0.47/srclib/apr-util/build/apu-conf.m4
--- source/httpd-2.0.47/srclib/apr-util/build/apu-conf.m4   2003-05-28
02:56:21.000000000 -0700
+++ build/httpd-2.0.47/srclib/apr-util/build/apu-conf.m4    2003-11-30
16:54:49.000000000 -0800
@@ -135,9 +135,9 @@
   apu_db_lib=db4
   apu_db_version=4
   ], [
-  AC_CHECK_LIB(db-4.0, db_create, [
+  AC_CHECK_LIB(db-4, db_create, [
   apu_db_header=db4/db.h
-  apu_db_lib=db-4.0
+  apu_db_lib=db-4
   apu_db_version=4
   ])])])
 if test "$apu_db_version" != "4"; then
Comment 1 Joe Orton 2004-06-04 13:32:47 UTC
I don't think I've seen a libdb-4.so created; what platform is this on?  The bdb
detection code was enhanced since 2.0.47; maybe you could try 2.0.49 to see if
it works out of the box?  Please re-open if there are still issues with 2.0.49.