Bug 46273 - Copy and paste error in M4 code causes APU configure to fail to look for Berkeley DB 4.5 as ordered
Summary: Copy and paste error in M4 code causes APU configure to fail to look for Berk...
Status: RESOLVED FIXED
Alias: None
Product: APR
Classification: Unclassified
Component: APR-util (show other bugs)
Version: 0.9.15
Hardware: All All
: P5 minor (vote)
Target Milestone: ---
Assignee: Apache Portable Runtime bugs mailinglist
URL:
Keywords: PatchAvailable
Depends on:
Blocks:
 
Reported: 2008-11-23 22:27 UTC by Matthew Sanderson
Modified: 2008-11-23 23:31 UTC (History)
0 users



Attachments
When instructed to build APU against Berkeley DB 4.5, look for BDB 4.5, not for BDB 4.4. (345 bytes, patch)
2008-11-23 22:27 UTC, Matthew Sanderson
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Matthew Sanderson 2008-11-23 22:27:53 UTC
Created attachment 22919 [details]
When instructed to build APU against Berkeley DB 4.5, look for BDB 4.5, not for BDB 4.4.

Overview:

What seems like a copy-n-paste error in the M4 autotools stuff in srclib/apr-util/build/dbm.m4 causes APU's configure to fail to look for Berkeley DB 4.5 when told to do so.
configure goes looking for Berkeley DB 4.4 instead, even though I explicitly said --with-dbm=db45.
Patch attached.

Steps to Reproduce:

Attempt to build HTTPd 2.0.63 against Berkeley DB 4.5 on a system that does not have Berkeley DB 4.4 installed.

Actual Results:

Build process stops due to failure to find Berkeley DB version 4.4, which is not installed.

Expected Results:

Build process should successfully build APU (and thus also HTTPd) against installed and working copy of Berkeley DB 4.5 as instructed.
(This actually occurs with attached patch applied.)

Build Date & Platform:

Building HTTPd 2.0.63 (and bundled APU 0.9.15) from released source tarball on a Linux/x86 system. Building both in one ./configure/make step - ie not APR, then APU, then Apache separately.

Additional Builds and Platforms:

Probably would occur on any other UNIX system, too; but I have not verified this.
Comment 1 William A. Rowe Jr. 2008-11-23 23:31:18 UTC
Already fixed in 1.3, your patch is applied in the unlikely event there is
another 0.9.x legacy release.  Thanks!