At 16:34 15/01/2003 +0100, Jérôme Augé wrote:
OK, I've installed this, but I would like one more go at getting the RPM working, so I don't get more problems when the next RPM is released - I guess I have to choose one method to follow, but am more used to dealing with RPM's.You must install the "httpd-devel" package, /usr/sbin/apxs is in this package.
> I reinstalled the mod_perl-1.99_05-3 RPM thinking that might give me lessI did, and the log showed the normal startup messages with no errors.
> problems, it looked OK but now:
>
> [Wed Jan 15 14:37:02 2003] [error] failed to resolve handler
> `ModPerl::Registry::handler'
> [Wed Jan 15 14:43:12 2003] [error] [client 192.168.1.30] Can't locate
> ModPerl/Registry/handler.pm in @INC (@INC contains: [snip]
>
> ... this is using the default conf.d/perl.conf that comes with the RPM (all
> I changed was the <Directory ...> location to one which used to work):
>
> LoadModule perl_module modules/mod_perl.so
> # [snip]
> <Directory /home/httpd/html/mp>
> SetHandler perl-script
> PerlHandler ModPerl::Registry::handler
> PerlOptions +ParseHeaders
> Options +ExecCGI
> </Directory>
>
> @INC includes /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi
> and I have:
> /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/ModPerl/Registry.pm
>
> .... but this is going into the realms of general Perl questions ...
>
> I'm wondering what I need to tweak to get the RPM to work, or a working
> parameter to pass to Makefile.PL
>
Did you stopped and restarted httpd after installing the package ?
I also tried creating a handler, as per "Getting Your Feet Wet with mod_perl" and again it failed to resolve the handler. And again I could see the path in @INC, the module was chown'ed to the user apache is running as, and it has wide-open file permissions.
This RPM was working before, so all my messing around has broken something I can't find. If the recommendation is to ditch the RPM and proceed with the new binary then that's fine.
thanks again, jon