1. Problem Description:
When I run make test I receive the following message
/usr/local/apache2/bin/httpd -d /usr/src/mod_perl-1.99_10/t -f /usr/src/mod_perl-1.99_10/t/conf/httpd.conf -DAPACHE2 -DPERL_USEITHREADS using Apache/2.0.47 (prefork MPM)
waiting for server to start: .Syntax error on line 14 of /usr/src/mod_perl-1.99_10/t/conf/extra.conf: Invalid command 'PerlSwitches', perhaps mis-spelled or defined by a module not included in the server configuration !!! server has died with status 255 (t/logs/error_log wasn't created, start the server in the debug mode) make: *** [run_tests] Error 143
Stas, I tried running this grep command (grep LoadModule t/conf/httpd.conf | grep -v PerlLoadModule)but it did not return anything.
Something I did find in httpd.conf was this, is this a problem? <IfModule !mod_perl.c> #unable to locate mod_perl.so (could be a static build) </IfModule>
Yup, you have pinpointed the problem. I have never seen this problem with mod_perl itself. There are quite a few scenarios where it can happen with third party modules using Apache::Test.
So let's figure out why it couldn't find mod_perl.so. Do you have src/modules/perl/mod_perl.so? If so do file perms look alright?
Try tracing the config phase first, by running:
t/TEST -trace=debug -config
and you should see what's going on, it'll report whether it can find mod_perl.so or not. e.g. on my machine it looks like:
/home/stas/apache.org/mp2> t/TEST -trace=debug -config setting ulimit to allow core files ulimit -c unlimited; t/TEST -trace=debug -config inheriting config file: /home/stas/httpd/prefork/conf/httpd.conf inheriting config file: /home/stas/httpd/prefork/conf/ssl.conf Found: perl_module => mod_perl.c Skipping LoadModule of mod_perl.c cleaning out current configuration ...
if it's reports that it can't find the perl_module (which is most likely what will happen), could you venture into Apache-Test/lib/Apache/TestPerlRun.pm and see why it can't find that file? It's plain perl so should be easy to debug. Thanks Tim.
Also, I don't have anything in the t/logs directory so I'm not able to send you that. Also, the docs about reporting problems mentions something about re-running the make test in verbose mode. But I'm not exactly sure how to do that for this situation. If you could give me an exact statement that would be helpful.
sure, since the server didn't start there will be nothing in the logs. Your bug report gives us most of the information that we need.
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
