Mailing-List: contact apreq-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 11 Dec 2003 01:52:37 -0500
Message-Id: <200312110652.hBB6qb7Z028094@alderaan.gsfc.nasa.gov>
From: "Edward J. Sabol" <sabol@alderaan.gsfc.nasa.gov>
To: apreq-dev@httpd.apache.org
In-reply-to: <Pine.LNX.4.56.0312110000300.7355@theoryx5.uwinnipeg.ca> (message
	from Randy Kobes on Thu, 11 Dec 2003 00:01:39 -0600 (CST))
Subject: Re: [ar2] PATCH: Set PERL_PATH correctly in Makefile.PL
References: <200312110528.hBB5Sd7Z027955@alderaan.gsfc.nasa.gov>
 <Pine.LNX.4.56.0312110000300.7355@theoryx5.uwinnipeg.ca>

Randy wrote:
> Thanks, Ed - the above works fine on my Win32 system.

Thanks for testing it, Randy.

Unfortunately, this patch doesn't solve the identical problem with "make
test". Apache::TestMM is generating the t/TEST scripts incorrectly.
Apache::TestMM wraps ExtUtils::MakeMaker, so you'd think it would get it
right, but it also inherits some functionality from Apache::Build. And
Apache::Build overrides ExtUtils::MakeMaker's value of $(PERL) with it's own
value obtained from my old nemesis, $Config{perlpath}. From the code, it
would appear that Apache::Build is doing it intentionally, but the reasoning
eludes me. And it's not clear if the problem should be fixed in Apache::Build
or just in Apache::Test. Perhaps I should continue this aspect of the
discussion to test-dev@httpd.apache.org?

Or I could just break down and ask my system administrator to change
Config.pm to have the correct value for $Config{perlpath}... Nah, that would
be too easy! :-)