The first bug is a known one: apparently, recent mod_perls are sensitive to the syntax of the <Perl> tag: they require a space in it, like this: <Perl > I hope this is just a bug that hasn't risen to the top of the priority list yet, and that the mod_perl folk don't intend to keep this sytax.
this is due to a limitation of apache 2.0. there _may_ be a way around it, but probably not any time soon.
Once that was fixed, I found a new problem. I recieved errors like this:
Syntax error on line 1059 of /etc/httpd/conf/httpd.conf:
Bareword "Apache::OK" not allowed while "strict subs" in use at /usr/lib/perl5/site_perl/5.8.0//i386-linux-thread-multi/Apache/PerlSection.pm line 47.!BEGIN not safe after errors--compilation aborted at /usr/lib/perl5/site_perl/5.8.0//i386-linux-thread-multi/Apache/PerlSection.pm line 58.!Compilation failed in require at (eval 57) line 3.!
try this patch, which was introduced after 1.99_09
Index: lib/Apache/PerlSection.pm =================================================================== RCS file: /home/cvspublic/modperl-2.0/lib/Apache/PerlSection.pm,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- lib/Apache/PerlSection.pm 7 Oct 2002 15:45:52 -0000 1.3 +++ lib/Apache/PerlSection.pm 20 May 2003 01:20:09 -0000 1.4 @@ -7,6 +7,10 @@
use Apache::CmdParms (); use Apache::Directive (); +use APR::Table (); +use Apache::Server (); +use Apache::ServerUtil (); +use Apache::Const -compile => qw(OK);
use constant SPECIAL_NAME => 'PerlConfig';
--Geoff
