On 1 Mar 2007 at 8:40, Perrin Harkins wrote: > On 3/1/07, Beginner <[EMAIL PROTECTED]> wrote: > > I have a number of handler configured like so: > > Apache2::Const qw(OK DECLINED NOT_FOUND); > > I don't see how this could work if you're really running mod_perl > 1.99. There is no module by that name in 1.99. > > > Would any one recommend a course of action? Should I remove the > > binary RPMs that my package manager installed and install from > > source? > > It is a good idea to use the latest mod_perl release, and it's not > hard to compile. I usually suggest compiling your own rather than > using an old one from your vendor. >
I had started going down the road of compiling from source. More interesting things popped up. ExtUtils reports that mod_perl2 -- 1.999022 is installed. mod_perl2? There are also three mod_perls under my lib dir: ~perl5/site_perl/5.8.5/i386-linux-thread-multi/auto/mod_perl2 ~perl5/vendor_perl/5.8.5/i386-linux-thread-multi/mod_perl.pm ~perl5/vendor_perl/5.8.5/i386-linux-thread-multi/auto/mod_perl This can't be good! When I tried to do `perl Makefile.PL MP_APXS=/path/to/apxs it complained: mod_perl/1.99_16 installation detected... not ok Cannot install mod_perl/2.0.3 on top of mod_perl/1.99_16 due to a major API change between mod_perl 1.999_21 and 1.999_22. Conflicting file: /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread- multi/Apache2.pm Conflicting dir: /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread- multi/Apache ...snip I should upgrade, or rather remove both Apache and all traces of mod_perl and start again. My problem is that I do have a few handlers that work and are used a bit throughout the day. There will no doubt be some modify to do to these to get them up again. Thanx, Dp.
