merlyn has asked for the wisdom of the Perl Monks concerning the following question:
Is there some secret option I should have applied? Is this particular to OSX, or is 5.10.1 in general incompatible with mod_perl 2.0.4?mod_perl.c: In function 'modperl_shutdown': mod_perl.c:62: error: 'my_perl' undeclared (first use in this function +) mod_perl.c:62: error: (Each undeclared identifier is reported only onc +e mod_perl.c:62: error: for each function it appears in.) mod_perl.c: In function 'modperl_hook_post_config_last': mod_perl.c:718: error: 'my_perl' undeclared (first use in this functio +n) mod_perl.c: In function 'modperl_child_exit': mod_perl.c:814: error: 'my_perl' undeclared (first use in this functio +n) mod_perl.c: In function 'modperl_response_handler': mod_perl.c:1036: error: 'my_perl' undeclared (first use in this functi +on) mod_perl.c: In function 'modperl_response_handler_cgi': mod_perl.c:1079: error: 'my_perl' undeclared (first use in this functi +on) make[1]: *** [mod_perl.lo] Error 1 make: *** [modperl_lib] Error 2
-- Randal L. Schwartz, Perl hacker
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: perl5.10.1 doesn't play well with mod_perl2 2.0.4 (or even beta) on OSX
by Khen1950fx (Canon) on Aug 08, 2010 at 08:04 UTC |