Thanks Gus, It maybe better for me to hunt around for a post API release for Hoary then. I'll check backports.
Regards, Ashley On Sun, 2005-08-28 at 16:46 +0100, Angus Lees wrote: > At Sat, 27 Aug 2005 13:30:42 +1000, Ashley Maher wrote: > > I loaded the mod perl2 package into Ubuntu. > > > The registery scripts worked well. > > > > The handler modules test failed misserably. > > > mod_perl/1.99_14 Perl/v5.8.4 PHP/4.3.10-10ubuntu4 configured -- resuming > > normal operations > [...] > > [Sat Aug 27 12:39:46 2005] [error] [client 127.0.0.1] Can't locate > > Apache2/RequestRec.pm in @INC (@INC > > contains: /usr/lib/perl5/Apache2 /var/www /etc/perl > > /usr/local/lib/perl/5.8.4 /usr/local/share/perl/5.8.4 /usr/lib/perl5 > > /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 > > /usr/local/lib/site_perl . /etc/apache2/ /etc/apache2/lib/perl) at > > /var/www/MyApache2/Rocks.pm line 8.\nBEGIN failed--compilation aborted at > > /var/www/MyApache2/Rocks.pm line 8.\nCompilation failed in require at (eval > > 4) line 3.\n > > mod_perl2 changed the names of the critical libraries in one of the > late prereleases (in order to avoid compatibility problems with > mod_perl1) > > You are using a pre-API-change mod_perl2 with code written from > post-API-change documentation. > > Basically the pre-API-change stuff was to "use Apache2" somewhere and > then use "Apache::RequestRec", etc (ie without the "2" on the prefix). > I don't have a box handy with pre-API-change mod_perl2 handy, but you > should be able to work things out by looking at what files you > actually have below /usr/lib/perl5/Apache2/. > > Be aware that any code you right to this API will not work against the > released version of mod_perl2 (it was released too late into the sarge > release process to make it into that release unfortunately). In most > cases the changes are a simple search+replace however. > -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
