Can you try downloading AxKit again from a known-good source like CPAN or axkit.org?
Did this from several sources and they all fail. Conclusion is that I have some rogue Perl code somewhere. Problem is, I'm not a Perl user, so what's there must be whatever default RH9 installs, as I've never consciously downloaded or added/deleted anything to it.
OK, from what I've heard from elsewhere Red Hat shipped a broken perl with RH9 - a build from CVS. Why oh why do we have to put up with this crap from Red Hat I don't know...
Anyway, the best fix I can think of for you is to install a new perl in a non-default location. If you run perl's configure it should use /usr/local rather than Red Hat's /usr for the location of perl, so this should work just fine for most scripts and leave your current Red Hat perl in-tact. Perl always makes bin/perl a symlink to bin/perl<version> anyway, so if it overwrites your bin/perl with a newer one you can always restore the old link so your system scripts continue to function.
So what you basically want to do is download perl 5.8.0 from perl.org or perl.com or direct from cpan. Then compile and install that (it's very straightforward - just run "sh Configure -de" after downloading it and entering the new directory, then run "make", "make test" and "make install" (last part as root) and it'll all "just work"). Then you need to build mod_perl-1.27 using this fresh perl, which should be installed as /usr/local/bin/perl5.8.0.
All sounds quite complex, but if you're careful to always use your "newer" perl it should all fall into place quite happily.
Matt.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
