o untar all distributions into a working directory
o ./configure apache with all the usual options I use (i have a script that has this):
./configure --with-perl=/usr/local/bin/perl --enable-module=rewrite --enable-module=include --enable-module=info --enable-module=usertrack --server-gid=nogroup --suexec-docroot=/usr/local/apache/htdocs --enable-module=most --enable-module=auth_db --enable-module=mmap_static --enable-shared=max --enable-module=ssl --enable-rule=SHARED_CORE --add-module=src/modules/dosevasive/mod_dosevasive.c --activate-module=src/modules/perl/libperl.a
o enter mod_ssl configure with apache
o enter mod_ssl directory and configure with these makepl options:
APACHE_PREFIX=/usr/local/apache APACHE_SRC=../apache_1.3.27/src DO_HTTPD=0 EVERYTHING=1 ALL_HOOKS=1 PERL_SSI=1 PERL_SECTIONS=1
o return to apache directory, re-run my configure script to activate the modules, build, and install.
Doing an httpd -l shows this now:
# /usr/apache/bin/httpd -l
Compiled-in modules:
http_core.c
mod_so.c
mod_dosevasive.c
mod_perl.c
suexec: disabled; invalid wrapper /usr/apache/bin/suexec (weird, I did a fresh install)
So I'll be damned if building mod_perl is such a pain in the arse. I hope Apache2 and MP2 will have an easier approach (I'm waiting on Apache2 for it to stabilize).
Ged, thoughts on this one? I of course still need to test mod_perl with something - will try my go at installing RT or something simple (open to suggestions).
Forrest
