On Thu, 29 Jul 2004, Alexey Bozrikov wrote: > Just applied all 'latest and greatest' patches, everything builds OK, > while same result during tests: > > [quote] > powerpc bozy: /home/bozy/src/modperl-2.0 $ t/TEST -verbose -debug -apxs [ ... ] > [Thu Jul 29 10:12:58 2004] [error] Can't locate > TestModperl__request_rec_Key_set_in_Base in @INC (@INC > contains: /home/bozy/src/modperl-2.0/t/lib > /home/bozy/src/modperl-2.0/Apache-Test/lib > /home/bozy/src/modperl-2.0/t/response > /home/bozy/src/modperl-2.0/t/protocol > /home/bozy/src/modperl-2.0/t/preconnection > /home/bozy/src/modperl-2.0/t/hooks > /home/bozy/src/modperl-2.0/t/filter > /home/bozy/src/modperl-2.0/t > /home/bozy/src/modperl-2.0/t/htdocs/testdirective/main > /home/bozy/src/modperl-2.0/t/htdocs/testdirective/perlmodule-vh > /home/bozy/src/modperl-2.0/t/ > /home/bozy/src/modperl-2.0/t/lib/perl > /home/bozy/src/modperl-2.0/blib/lib > /home/bozy/src/modperl-2.0/blib/arch > /usr/local/lib/perl5/5.8.4/aix /usr/local/lib/perl5/5.8.4 > /usr/local/lib/perl5/site_perl/5.8.4/aix > /usr/local/lib/perl5/site_perl/5.8.4 > /usr/local/lib/perl5/site_perl) at (eval 15) line 1.\n > [Thu Jul 29 10:12:58 2004] [error] Can't load Perl file: > TestModperl__request_rec_Key_set_in_Base for server :8529, > exiting... > [Thu Jul 29 10:12:58 2004] [error] $s->add_config() has > failed: init mod_perl vhost failed during global > destruction.\nCompilation failed in require at > /home/bozy/src/modperl-2.0/t/conf/modperl_startup.pl line > 17 during global destruction.\n\t...propagated at (null) > line 94.\nBEGIN failed--compilation aborted at > /home/bozy/src/modperl-2.0/t/conf/modperl_startup.pl line > 20.\nCompilation failed in require at (eval 2) line 1.\n > [Thu Jul 29 10:12:58 2004] [error] Can't load Perl file: > /home/bozy/src/modperl-2.0/t/conf/modperl_startup.pl for > server localhost:8529, exiting... > [unquote] > > Now, during build I've noticed that static version of mod_perl could be > built as well (LINKTYPE appeared during `make'). How this could be done? > I just want to make sure it's not a compiler problem, cause if static > build test fails - then most probably incorrect code is generated. >
Assuming this is for the dynamic build, that LINKTYPE might have been the one added in the patch as an addition to making the aprext target, so as to build a static aprext lib. Apart from the PerlSetVar TestModperl__server_rec_Key_set_in_Base SubSecValue in t/conf/httpd.conf, are there any other occurrences of TestModperl__server_rec_Key_set_in_Base in anything under t/*? Are there error in the ModPerl-Registry tests? cd ModPerl-Registry make test -- best regards, randy -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html