I've also seen this at the install level, on a fresh install (otherwise, as you say, it picks things up in the system perl tree). I guess it's because @INC should also include blib/lib? I've just set PERL5LIB to get around this, for now.
yeah, I think it's related to the latest change in ModPerl::MM
http://marc.theaimsgroup.com/?l=apache-modperl-cvs&m=104432362926275&w=2
removing -MApache2 from the macro solves the problem, but thus makes it unusable for third party modules.
I guess we really need to think harder about third party module support. I know I've struggled with this lately as has Stas, although ModPerl::MM::WriteMakefile seems to sorta work.
maybe we should just revisit third party modules alltogether and come up with a feature list and API, then implement from scratch - possibly as a ModPerl::MM subclass or something.
--Geoff
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
