On Sat, Jul 08, 2006 at 12:01:20PM +0200, Toni Mueller wrote: > > Hello, > > while still working on that INN port, I found the following problem I > couldn't yet solve: > > I'd like to run --with-berkeleydb for a "better" overview style, but > the process fails to find either includes or libs of db4 correctly. > I've looked into the top level 'configure' file which is generated by > autoconf 2.13, but which has settings incompatible with OpenBSD. It > doesn't handle the splitting that's in OpenBSD, but also no independent > set of variables which I could set to achieve that effect manually. > Trying to fiddle with COPTS in the master Makefile was ineffective, as > was 'man bsd.port.mk' and then searching for autoreconf. > > How do I best rebuild a configure file from a given configure.in, then?
You usually set CONFIGURE_STYLE=autoconf and let the infrastructure deal with it. autoreconf/autoconf are in meta-auto, and you have to set AUTOCONF_VERSION correctly. Beware ! one big issue is that autoconf 2.13 might not be autoconf 2.13. There was a huge gap where the FSF did not publish any official updates, and so quite a few configure files `generated by autoconf 2.13' actually correspond to mutant development versions. The FSF itself is quite guilty of that. As far as software engineering, they have a very hazy notion of `release' and of `loose coupling'. Quite a few of their basic packages live in very incestuous relationship and tend to depend on semi-documented internals of never released versions. (to wit, gcc, binutils, libtool, autoconf, glibc, newlib, libiberty tend to have very tight couplings that prevent independent updates and force duplication of codes. e.g., close to the `dll hell' anti-pattern).
