(I'm not sure if I should continue posting these reports to the list. Please let me know if I should send them to just you.)
Stas Bekman wrote:
Oh, sorry, for some reason I thought you were talking about the static build. Could you please post the output of:
t/TEST -conf -trace=debug
I downloaded the latest httpd (2.0.52) and the CVS version of mod_perl as of ~1600 California time.
Running this command results in:
[EMAIL PROTECTED] modperl-2.0]# t/TEST -conf -trace=debug
[ debug] loading custom config data from: '/usr/local/src/modperl-2.0/lib/Apache/TestConfigData.pm'
[ debug] configuring httpd
something is wrong, mod_perl 2.0 build should have supplied all the needed information to run the tests. Please post lib/Apache/BuildConfig.pm along with the bug report at /usr/local/src/modperl-2.0/Apache-Test/lib/Apache/TestConfig.pm line 349.
The bug report shows the same problem as before - that httpd couldn't be found.
Also this shouldn't affect things, but any difference if you set APACHE_TEST_NO_STICKY_PREFERENCES=1 env var?
APACHE_TEST_NO_STICKY_PREFERENCES=1 t/TEST -conf
No.
By the way, I also tried to build the static version using the command
perl Makefile.PL MP_USE_STATIC=1 MP_AP_PREFIX=/usr/local/src/httpd-2.0.52
This resulted in the following error message:
Reading Makefile.PL args from @ARGV MP_USE_STATIC = 1 MP_AP_PREFIX = /usr/local/src/httpd-2.0.52 [ error] You specified MP_USE_STATIC but did not specify the arguments to httpd's ./configure with MP_AP_CONFIGURE
Is this correct? Since I don't use any arguments to ./configure when I build httpd why do I need to use the MP_AP_CONFIGURE option?
-- 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
