It's been a long awaited feature, to bring back something similar to the old mod_perl option to have mod_perl statically linked to httpd. Here is my attempt at it.
You rock, this looks so simple :)
The original way I attempted this was to hook into the new httpd build system, but, one issue about that is that it would require autoconf/automake/aclocal.
So, instead, this patch tries to make things work by poking at httpd ever so slightly.
I doubt patching is the best route. Or at least we should support both ways - e.g. if there is autoconf/automake/aclocal then use that, otherwise use patching? I guess autoconf staff is a lot of stuff to write? BTW, libapreq2 added static linking recently, have you looked at how it performs that? (I haven't yet).
There is currently one bug with mod_perl compiled statically. It tries to add the MODPERL2 server define at hook-registry phase, but for statically linked modules, that hook-registry phase is called before ap_server_config_defines is created.
so may be we can dynamically add some hook to insert the define at a later time?
The patch looks fine to me, but if it makes it in static build will require 2.0.50?
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
