Bug 40266 - berkeley db support in httpd is screwed
Summary: berkeley db support in httpd is screwed
Status: NEEDINFO
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Core (show other bugs)
Version: 2.5-HEAD
Hardware: PC Linux
: P2 blocker (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-16 11:56 UTC by Martin J. Green
Modified: 2017-03-02 11:12 UTC (History)
1 user (show)



Attachments
configure log (64.92 KB, text/plain)
2006-08-16 13:13 UTC, Martin J. Green
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Martin J. Green 2006-08-16 11:56:21 UTC
Berkeley db support is either absolutely fucked up in httpd2, or is just a 
mess. 

Problem 1
When you select --with-berkley-db, apr and apr-util are no longer built.

Problem 2
When you compile apr and apr-util manually, it doesn't pick up the path to db4 
you gave it and instead makes up its own (with spaces in) which of course 
fucks up the compile.

I'm sure there's more to come, but I've been wrestling with this for hours. So 
utterly pissed off that something so simple is causing such a headache.
Comment 1 Martin J. Green 2006-08-16 12:25:15 UTC
THIS BUG IS *NOT* FIXED!!!!
Comment 2 Joe Orton 2006-08-16 12:44:23 UTC
I think you added your "Problem 3" to the wrong bug (bug 25233)?

The option is "--with-berkeley-db", note the spelling.  w.r.t. Problem 1, please 
capture the configure output and add it to this report as an attachment.  Please
also attach the "config.log" file which is produced.
Comment 3 Martin J. Green 2006-08-16 13:12:23 UTC
configure is as follows...

CFLAGS="-O2 -pipe -march=nocona -mtune=nocona -fomit-frame-pointer" 
CXXFLAGS=$CFLAGS \
./configure \
--enable-layout=Slack \
--enable-modules=most \
--enable-so \
--disable-cgid \
--disable-speling \
--disable-ldap \
--disable-proxy \
--enable-rewrite=shared \
--enable-include=shared \
--enable-ext-filter=shared \
--enable-env=shared \
--enable-expires=shared \
--enable-headers=shared \
--enable-setenvif=shared \
--enable-dav \
--disable-status \
--disable-info \
--enable-asis=shared \
--enable-vhost-alias=shared \
--enable-imap=shared \
--enable-actions=shared \
--enable-mime-magic=shared \
--enable-ssl=shared \
--with-included-apr \
--with-berkeley-db=/usr/include/db4:/lib64 \
--enable-dbd \
--build=x86_64-slackware-linux

I'll attach config.log too

I can now get apr and apr-util to compile by using --with-included-apr (I 
didn't need to before berkeley-db was added), but it still doesn't appear to 
be compiling bdb in - I can't access svn.
Comment 4 Martin J. Green 2006-08-16 13:13:21 UTC
Created attachment 18720 [details]
configure log
Comment 5 Martin J. Green 2006-08-16 13:53:58 UTC
when compiled with bdb (apparently), I see...

[Wed Aug 16 15:55:07 2006] [crit] (70023)This function has not been 
implemented on this platform: DBD: failed to initialise
[Wed Aug 16 15:55:07 2006] [crit] (70023)This function has not been 
implemented on this platform: DBD: driver for [DBDriver unset] not available
[Wed Aug 16 15:55:07 2006] [crit] (70023)This function has not been 
implemented on this platform: DBD: failed to initialise
[Wed Aug 16 15:55:07 2006] [notice] Apache/2.2.3 (Unix) DAV/2 mod_ssl/2.2.3 
OpenSSL/0.9.7g SVN/1.3.2 configured -- resuming normal operations
[Wed Aug 16 15:55:07 2006] [crit] (70023)This function has not been 
implemented on this platform: DBD: driver for [DBDriver unset] not available
[Wed Aug 16 15:55:07 2006] [crit] (70023)This function has not been 
implemented on this platform: DBD: failed to initialise


whenever I try and access svn with bdb storage
Comment 6 Joe Orton 2006-08-16 14:35:37 UTC
The "DBD: " lines are from mod_dbd, not directly related to Berkeley DB (aka BDB).

It always emits those "critical" errors if not explicitly configured IIRC;
that's not a symptom of anything being wrong.

Please attach the *output* of the configure command too ("configure ... >
/tmp/output").  If you want to diagnose problems with APR-util detecting
Berkeley DB, please also attach the file "srclib/apr-util/config.log"; but this
is problem 2.
Comment 7 Martin J. Green 2006-08-16 15:44:28 UTC
I'm not even sure that its apache not including berkeley - the only conclusion 
I could reach, since its supposed to be compiled in and svn will happily 
create a BDB repo, but when apache tries to access it, it gives a 500 & dumps 
a pile of errors.
Comment 8 Karl Southern 2006-09-27 09:47:10 UTC
I have had similar problems with APR, SVN and Apache. Basically it involved
deleting the bundled apr libraries that came with SVN, and then pointing it at
the apache libraries (--with-apr=/www/bin/apr-1-config
--with-apr-util=/www/bin/apu-1-config). This appears to work for me - although
it may not be the same problem? Sorry if its not :)