Oden Eriksson wrote: [...]
Please post the output of: % t/TEST -conf -trace=debug
Attached.
So it has matched it as revision 1:
> [ debug] Matched Apache revision Apache-PREFORK-AdvancedExtranetServer/2.0.52 1
Frankly I have no idea how could it possibly happen.
And that's where the problem is coming from.
Please try this patch:
Index: lib/Apache/TestServer.pm
===================================================================
--- lib/Apache/TestServer.pm (revision 124937)
+++ lib/Apache/TestServer.pm (working copy)
@@ -67,15 +67,9 @@
# string and various variations made by distributions which mangle
# that string- # Apache/2.0.50-dev
- ($self->{rev}) = $self->{version} =~ m|^Apache/(\d)\.|;
+ # Foo/x.y.z
+ ($self->{rev}) = $self->{version} =~ m|/(\d)\.|;- # Apache-AdvancedExtranetServer/1.3.29 (Mandrake Linux/1mdk)
- ($self->{rev}) ||= $self->{version} =~ m|^Apache.*?/(\d)\.|;
-
- # IBM_HTTP_SERVER/1.3.19 Apache/1.3.20 (Unix)
- ($self->{rev}) ||= $self->{version} =~ m|^.*?Apache.*?/(\d)\.|;
-
if ($self->{rev}) {
debug "Matched Apache revision $self->{version} $self->{rev}";
}I think what happens is this. MP_INST_APACHE2=1 tweaks Makefile to insert mp2 modules into Apache2 subdir, but since you use a custom INSTALLDIRS it fails to do that. And then:
if ($rev == 2) { eval { require Apache2 && require mod_perl }; } else { eval { require mod_perl }; }
loads modperl1.
but I've just tried here with the same options and it works fine.
I also tried to leave out MP_INST_APACHE2=1 as well as not having mod_perl-common-1.3.31_1.29-3mdk installed.
I just saw this:
Warning: the following files are missing in your kit: META.yml
But the file is there.
It's possible that Apache-Test/Makefile.PL is the one that has complained. But ignore that for now.
A-T is bundled with modperl and it's the one that should be run. Not any previously installed A-T.
The system is clean except for parts of mod_perl 1.x that seems to be a requisite to get this mod_perl pick up missing pieces. Here's what's installed:
what do you mean requisite? you mean mp2 requires mp1?
Maybe it's a thing of the past, or I'm just too tired right now. At one time I saw something like "Found mod_perl-1.x, good, will install relatively to Apache2/". And that message was despite the MP_INST_APACHE2=1 thing.
Hmm, do you think it's a misleading message? I guess we could remove it if MP_INST_APACHE2=1 is used explicitly.
-- __________________________________________________________________ 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
