perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From William Bulley <>
Subject Re: apache2 or mod_perl2 oddball error
Date Fri, 17 Jun 2011 21:05:08 GMT
According to Fred Moyer <> on Fri, 06/17/11 at 16:22:
> I think Perrin is right, I've never seen -compile syntax used in
> PerlModule directives.  Move the PerlModule directives into a
> file.
> In your httpd.conf:
> LoadModule perl_module        modules/
> PerlPostConfigRequire /my/
> In your
> #!/usr/bin/perl
> use strict;
> use warnings;
> # make sure we are in a sane environment.
> $ENV{MOD_PERL} or die "GATEWAY_INTERFACE not Perl!";
> use Apache2::Const -compile => ':common';
> ... add any other PerlModule statements in the 'use Module' format.

Fine.  But what has this got to do with the inability of the apache
server to start?  These PerlModule directives are not my idea.  They
came with the application in question (to which I am trying to get).

Once I get the apache server running, I can deal with issues like
this one.  BTW, the application in question does not have a startup
file, it just has an index.html file and uses Mason, but that is
neither here nor there as far as this problem is concerned.

Recall that with these two "Const -compile" lines commented out
of that include file, the syntax phase of "apachectl -t" succeeds,
but the server does not start, and a bunch of other errors appear.

This, to me, sounds like an issue between apache2 and Perl 5.14 or
between mod_perl2 and Perl 5.14, but I don't really have any clue.



William Bulley                     Email:

72 characters width template ----------------------------------------->|

View raw message