Randy Kobes wrote:
On Thu, 27 Nov 2003, Stas Bekman wrote:

[ .. ]

Search your filesystem, you must have Apache/Response.pm
if you have installed mp2.

It seems that you have a messed up installation, as your
ModPerl/Registry.pm resides under non-Apache2 subdir and
you have /Apache/Apache2/lib/perl. Did you have some old
mod_perl install? Both ModPerl/Registry.pm and
Apache/Response.pm are supposed to live under the same
directory. I hope you didn't just go and copy
ModPerl/Registry.pm manually, leaving out the rest.


Actually, ModPerl::Registry appearing as a
lib/ModPerl/Registry.pm and Apache::Response appearing as a
lib/Apache2/Apache/Response.pm does happen with Win32,
which is different than Unix, where both appear
under a lib/Apache2/.

So is that a MakeMaker thing. It's a definite a bug and it needs to be fixed.


Though I'd check blib/ first. If the two don't reside under the same directory it may as well be a bug in ModPerl::BuildMM which arranges for 2.0 modules to be under Apache2/ subdir.

> That's why, if you miss loading
> the Apache2.pm module, ModPerl::Registry is found,
> but not Apache::Response.

It's just that Patricio's report had:

(@INC contains: D:/Perl/lib D:/Perl/site/lib .
D:/Apache/Apache2/ D:/Apache/Apache2/lib/perl)

with Apache2 in it, so for a moment I thought that he had Apache2 included. Does the ppm that you maintain include startup.pl or some other file, where we could include 'use Apache2;' on behalf of users? I guess they will still have to include it from httpd.conf, unless you supply the latter and we should just put it there then.

__________________________________________________________________
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


-- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html



Reply via email to