Tim Huffman wrote:
In this particular case it's not about being old, but about modperl
RPM
being built against one (older) version of Apache, and you're trying to use
it
against another (more recent version). But yes, save yourself a lot of trouble and get the latest Apache and mod_perl and install them from source.
When you see an error message like:
"mod_perl.c" is not compatible with this version of Apache (found 20020628, need 20020903)
That means that mod_perl was built against Apache released on or post-20020628, but you are trying to load it against one released on
or
post-20020903.
A properly made RPM must tell you that you don't have the right Apache installed before allowing you to install itself without forcing.
Thanks, I'll try building them from source. Do I need to uninstall the RPMs before I build from source? I'm also running Cacti/MySQL on this server (also installed from RPMs), are they going to break if I build from source? Thank you very much for your help!
Uninstall the rpm of mod_perl only and rebuild it from source. Ideally you want to use the latest Apache as well, so I'd suggest to get one first.
I don't know about the other modules. If you get problems with those you will have to ask at the appropriate forum.
-- __________________________________________________________________ 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
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
