> On Fri, Feb 20, 2004 at 12:15:59AM -0000, David Reid wrote: > > This improves the detection of the BerkeleyDB on FreeBSD. It basically > > correct what's looks like some copy/paste oversights (looking for db4 when > > in a db4.2 block for instance) and adds the ability of the apu_hints.m4 to > > pass in a platform_places to look for the directory. This is added to the > > user_places prior to checking any user supplied dirs. > > /usr/local is not FreeBSD specific: you should configure using > --with-berkeley-db=/usr/local. wrt to the db4 vs db4.2 this is > deliberate to cope with the various ways BDB is packaged. Is that > actually breaking for you, if so how?
Well as far as it goes , fair enough. BUT the configure script is supposed to be able to deal with this sort of nonsense isn't it? Otherwise what's the point? On a "plain vanilla" FreeBSD 4.9 system, with BDB 4.1 from ports, apr was failing to find the libs... The patch was intended to fix it. This seems like a common enough situation that it should be addressed. Sander pointed out some problems with the patch and so it needs a little bit of work as it fails on Linux systems... I also have some ideas about other small tweaks so I'll resubmit the patch (maybe later tonight). > > The patch also adds the APRUTIL_LIBS and _LDFLAGS to the link line for the > > final lib as otherwise it craps out when we try and use the lib during the > > httpd build :( > > This looks good but will this break the build with libtool 1.3 (since it > means that libaprutil*.la may get linked against other .la files)? That > needs to be checked. Yep, this doesn't seem to work as well as it might. Something needs to be done to get the correct link line though as without the change it won't allow us to build using it. I'll investigate. If you have ideas come see me on irc :) > (Fixing this means the EXTRA_OS_LINK hack in configure can be removed > too) Removing hacks is always a good plan... david
