mod_perl.c:
if (!modperl_config_apply_PerlRequire(s, scfg, perl, p)) {
exit(1);
}
if (!modperl_config_apply_PerlModule(s, scfg, perl, p)) {
exit(1);
}
Therefore the following fails:
PerlModule Apache2
PerlRequire "/home/httpd/httpd-2.0/perl/startup.pl"
if the startup file needs something from Apache2/ (which is in 99% the
case).
We cannot really solve it by swapping the order of applying PerlRequire
and PerlModule in mod_perl.c, because the opposite situation is quite
possible: the startup requires "Apache2.pm" and some PerlModule needs it.
So it seems to me is my previous suggestion of unconditional loading
Apache2 from the core is applied, this problem goes away.
__________________________________________________________________
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]
