I am having the exact same test failure results on openbsd, and the archives show that some people have had similar problems, with no resolution that I have seen.
what happens if you manually run /usr/local/apache2/bin/httpd -X -d ./t -f cont/httpd.conf from within the toplevel mod_perl-1.99_09 directory? the -X tells apache to run as a single process, no forking. the problem on openbsd is that the fork'd child processes are getting segfaults somewhere in libperl.so, but the parent process is doing its thing (fork'ing children) and returning successfully. I didn't post a bug report here because I think its a problem with perl on openbsd. Could this be a mod_perl problem? the segfaults are due to attempts to access mem 0xabababab which is a special value that perl uses (with the Poison macro) to try to make catching segfaults easier. I'm kinda stuck. Dave Eric Schwartz wrote: > *** setting ulimit to allow core files > ulimit -c unlimited; t/TEST -verbose=0 > /usr/local/apache2/bin/httpd -d /usr/local/src/mod_perl-1.99_09/t -f > /usr/local/src/mod_perl-1.99_09/t/conf/httpd.conf -DAPACHE2 > using Apache/2.0.46 (prefork MPM) > > waiting for server to start: ......[Wed Jun 04 00:11:21 2003] [info] 19 > Apache:: modules loaded > [Wed Jun 04 00:11:21 2003] [info] 3 APR:: modules loaded > [Wed Jun 04 00:11:21 2003] [info] base server + 8 vhosts ready to run > tests > ........................................................ > waiting for server to start: giving up after 61 secs > !!! server failed to start! (please examine t/logs/error_log) > make: *** [run_tests] Error 1
