Zac Morris wrote: > Ok, still no luck. Every dependancy has more dependancies all of which go > back and back to mod_perl 1 stuff already being in place.... > > > My question is, can I download the Apache 1.3 source (don't "make" it), then > run the mod_perl 1 build to get all the pm files in place, then rebuild my > mod_perl 2 (against my installed Apache 2 source).
Sorry Zac, my diagnosis and patch were wrong. mod_perl 2.0's compat layer doesn't require mod_perl 1.0 to be installed, sorry for confusing people. Apache::Module *is* in 2.0. But for some reason it didn't work for you. So let's try to investigate why. It seems to me that you have Apache::Module for 1.0 installed and it gets loaded instead of 2.0's version. Can you list all Apache/Module found on your machine (pm, so, etc)? locate Apache/Module I'm certain that if you install mod_perl 2.0 into Apache2/ dirs (even though you don't have mod_perl 1.0 installed) this problem will go away. But I'd still like to figure out what kind of collission you have now. > Also, we mentioned the whole "Bundle::Apache", will there be one of those > for Apache 2 and will it contain all the mod_perl 1 AND mod_perl 2 stuff to > allow running in Compat? no, it'll contain only stuff needed for 2.0, which may include modules that work for both mod_perls, but definitely not mod_perl 1.0. Again I apologize for my mistake. __________________________________________________________________ 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
