jean-frederic clere wrote:
>
> Cliff Woolley wrote:
> >
> > Hey guys...
> >
> > How are we doing on those 2.0.22 showstoppers?
> I have done:
> ./configure --prefix=/home/apache20/apache20 \
> --enable-mods-shared=all
> It also activates modules like auth_dbm even if no database support (compile
> errors).
mod_auth_dbm has bitten me twice recently, with compiler errors. If you
Google on the errors involving ndbm.h, you will see that Apache is
usually involved. I think that this module is a PITA, and is causing
our users more headaches than it should.
<rant>
I recently put Linux Mandrake 8.0 on my ThinkPad, tried to build Apache
2.0, and guess which module wouldn't compile? (hint: see above)
Googled, found out which obscure *-devel rpm on the 2nd CD provided
ndbm.h this time around, installed the rpm, then the final link of httpd
had unresolved references for dbm_open, dbm_close, etc. Couldn't figure
it out, disabled mod_auth_dbm, the build went fine. Later Victor & Jeff
found that my libdb1.so had no exported symbols. sheesh, what next?
Yeah, I know, this one sounds like a Mandrake packaging error.
</rant>
My point is that this stuff seems to be rarely used outside of Apache,
is in flux, and is a pain to folks who don't use it. Should we disable
mod_auth_dbm at autoconf time if the headers are missing?
Greg
