Hi, I'd greatly appreciate ideas on getting mod_perl successfully loaded via DSO into my Apache 1.3.33 installation.
I compile and receive no errors (via Makefile.PL or via direct apache compile).

I am not sure if I do not have my config file properly referencing mod_perl (I think it's right) or somehow the Makefile.PL mod_perl compile is not right, though the compile seems extremely straight-forward. I also tried an apache recompile (also using DSO) and same result, no compile errors, got a binary, no mod_perl.so but did get a libperl.so. Currently I tried overlaying libperl.so with the new mod_perl version. While nothing "bad" happened neither did anything "good".

 I compiled it standalone with:
perl Makefile.PL USE_APXS=1 WITH_APXS=/home/apache_1.3.33/src/support/apxs EVERYTHING=1 APACHE_SRC=../apache_1.3.33/src

it created libperl.so which I added to the folder Apache loads it's modules from. I stopped and started the server, then modified the httpd.conf to add:

 PerlModule Apache::Registry
  <Location /perl/>
      SetHandler perl-script
      PerlHandler Apache::Registry
      Options +ExecCGI
      PerlSendHeader On
      allow from all
  </Location>

and get "Invalid command 'PerlModule', perhaps mis-spelled or defined by a module not ...

I'm a bit confused by references to mod_perl.so vs libperl.so. From reading it seems there are historical reasons why they have the same name, but I see nothing to say if I should rename one of them or what. The httpd.conf references all say mod_perl:
<IfDefine HAVE_PERL>
AddModule mod_perl.c
</IfDefine>
<IfDefine HAVE_PHP>
.
.
.
<IfModule mod_perl.c>
    Alias /perl /var/www/perl
    <Directory /var/www/perl>
        SetHandler perl-script
        PerlHandler Apache::Registry
        Options +ExecCGI
    </Directory>
</IfModule>

Reply via email to