Kermit Tensmeyer wrote:
regarding changes in Build.pm to support threading.
In Apache::Build::mpm_name, gets the name by calling $self->apxs('-q' => 'MPM_NAME');
How does apxs (either standalone or Apache::Build::apxs) figure out MPM_NAME?
/usr/local/apache2/bin/apxs -q MPM_NAME
I assume that it would get it from the config file (the modperl version
being freeze of the $self object)
As near as I can gather, neither the Apache2 version of the config
file, nor the modperl-2.0 version of the file, contain the information.
$self->build_config loads every value listed in the file into ----- symptoms -----
perl Makefile.PL
Reading Makefile.PL args from /home/kermit/.makepl_args.mod_perl2
MP_AP_PREFIX = /usr/local/apache2
MP_DEBUG = 1
MP_INST_APACHE2 = 1
Configuring Apache/2.1.0-dev mod_perl/1.99_10-dev Perl/v5.8.0
Failed to obtain the MPM name at lib/Apache/Build.pm line 169.
I bet it's using the wrong apxs. do you have something in /usr/local/apache?
Apache::Build::apxs() seems pretty suboptimal to me. I've taken a few looks at it, trying to figure out how to make it better, but I haven't come across the perfect solution yet. when I use MP_APXS in my build arguments, it generally picks the proper apxs, though.
HTH
--Geoff
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
