On Saturday 25 June 2005 05:07 am, Danny Thomas wrote: > I want > 1) statically-linked mod_perl - mason 1.29_02 README might need updating > for mod_perl2 but currently says > Using Mason with a mod_perl DSO may cause your Apache server to > crash silently at startup, or fail intermittently. The fix for this problem > is to install Apache/mod_perl with mod_perl compiled statically into the > Apache binary.
I've been running mason on mp2 for quite a while without problems. It looks like mason finally supports mp2, so you shouldn't need the MasonX handlers either now. (I've not tried this yet though). > 2) built/installed as user www (need non-root for mod_perl testing > anyway) 3) install under /opt/apache > > http://perl.apache.org/docs/2.0/user/install is quite good, but it would be > good if it had a section on building a statically-linked mod_perl. Like this: http://perl.apache.org/docs/2.0/user/install/install.html#Static_mod_perl ? > Has anyone managed to compile a static (no DSO) apache with mod_perl and > libapreq? Both mod_perl and libapreq have instructions for building them > statically individually, but the instructions seem to be mutually > incompatible. As far as I know, you can't do it. I asked the same question a while back and got no answer at all. I couldn't find a way of doing it myself either. > SECOND ATTEMPT > since the destination directory is empty, use MP_AP_PREFIX to specify > "httpd's source tree" as asked for. > NB #MP_AP_PREFIX on the install page says > If Apache is not installed yet, you can point to the Apache 2.0 source > directory, but only after you've built or configured Apache in it. > which is a bit worrying as we've been told to skip the build/configure You need to configure apache first only if you are building modperl as a module. For a static modperl, you don't need to do it.
