Berkeley DB 4.0.14 (ebuild r2) is marked stable, but the latest stable Apache2 build (2.0.48-r1) doesn't bind to it. I've had to add "--with-dbm=db4 --with-berkeley-db=/usr \" to the Apache2 ebuild file. Ideally it should check for db4 and use only if installed.
I've inserted the following near the beginning of the src_compile() function in the ebuild: #detect if db >= 4 is installed db_ver=`grep 'DB_VERSION_MAJOR' /usr/include/db.h | cut -f3` if [ $db_ver >= 4 ]; then myconf="${myconf} --with-dbm=db4 --with-berkeley-db=/usr" fi I haven't had a chance to actually run the ebuild to make sure the 'myconf' handling is right (system is borked), but the rest works.
What errors do you get when your are compiling apache?
I didn't get any fatal compile errors, if that's what you mean. If I run 'apu-config --db-version' it returns '3' although Berkeley DB 4.0.14 is installed. Subversion (with mod_dav_svn) depends on Apache2 being compiled with Berkeley DB >= 4.0.14. It makes sense to me to have Apache use the appropriate configure flags when possible. I settled on this in my tweaks of the build file: if use berkdb; then db_ver=`grep 'DB_VERSION_MAJOR' /usr/include/db.h | cut -f3` if $db_ver == 4; then myconf="${myconf} --with-dbm=db4\ --with-berkeley-db=/usr" fi fi
This should be fixed in 2.0.49-r1. Thanks for the bug report. Regards, chuck
