Danny Thomas wrote:
I would be grateful if people could try the documented approach but
1) as non-root (which is always good when building software because
it makes it unlikely stuff gets accidentally installed in wrong location)
2) with a fairly clean file-system. I did a rm -rf of the ht
I was in a bit of a rush to send my original email.
I first tried doing things per #Static_mod_perl on the install page,
but after flailing around for a while thought I'd try a more methodical
approach as in my email. NB the approach documented on #Static_mod_perl
corresponds to my SECOND ATTEMPT,
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 intermi
Danny Thomas wrote:
I'm not sure whether it is a real bug, not properly documented or whether
I'm just being particularly thick, but I can't seem to build a statically-
linked apache2/mod_perl2
Danny,
FWIW, I used the following options to build static mod_perl/Apache2 on
CentOS 4 (httpd 2
I'm not sure whether it is a real bug, not properly documented or whether
I'm just being particularly thick, but I can't seem to build a statically-
linked apache2/mod_perl2
I want
1) statically-linked mod_perl - mason 1.29_02 README might need updating
for mod_perl2 but currently says
