[Module::Build] Re: Module::Build 0.27_09 -> CPAN

[Randy W. S. <ml...@th...>]

Andy Dougherty wrote:
>>> Ken Williams wrote:
> 
>>>> I've just released M::B 0.27_09 with the following changes.  In  
>>>> particular, when I use this copy of Module/Build.pm in bleadperl, all  
>>>> the M::B-related tests now pass (though with considerable complaining).
> 
> Alas, this still fails for me.  I build perl on Solaris with a symlink tree
> 
> 	sh ../perl-current/Configure -Dmksymlinks -Dprefix=/tmp/perl -des
> 
> and the Module Build tests still fail.  Here's a sample:
> 
> ../lib/Module/Build/t/basic..................................Can't locate Config.pm in @INC (@INC contains: /tmp/perl/lib/5.9.4/sun4-solaris /tmp/perl/lib/5.9.4 /tmp/perl/lib/site_perl/5.9.4/sun4-solaris /tmp/perl/lib/site_perl/5.9.4 /tmp/perl/lib/site_perl .).
> BEGIN failed--compilation aborted.
> Use of uninitialized value $perl in concatenation (.) or string at /home/doughera/src/perl/perl-andy/t/../lib/Module/Build/Base.pm line 1162.
> sh: -le: not found
> 
> Here's another sample:
> 
> ../lib/Module/Build/t/ext....................................PERL_CORE is set but I can't find your perl source!
> Bareword "our" not allowed while "strict subs" in use at /home/doughera/src/perl/perl-andy/lib/Config.pm line 21.
> Bareword "Config" not allowed while "strict subs" in use at /home/doughera/src/perl/perl-andy/lib/Config.pm line 21.
> Operator or semicolon missing before %Config at /home/doughera/src/perl/perl-andy/lib/Config.pm line 21.
> Ambiguous use of % resolved as operator % at /home/doughera/src/perl/perl-andy/lib/Config.pm line 21.
> BEGIN not safe after errors--compilation aborted at /home/doughera/src/perl/perl-andy/lib/Config.pm line 31.
> BEGIN failed--compilation aborted.
> 
> I think the other error messages here are because the test apparently
> picked up an older perl (probably 5.00503) installed elsewhere in my
> PATH.

This is what happens. It looks at several potential perls, and for each 
one, compares the configuration to see if it's the same perl that is 
currently executing. The problem is that when it executes the perl 
binary it finds in the core, it doesn't pass in the correct include 
directory for it to find Config.pm, so the test fails and it continues 
the search by looking in the PATH.

Attached is a working (not final) patch that works for me on FreeBSD, 
Ubuntu Linux, Windows XP, and cygwin. Could you please give it a spin?

Thanks,
Randy.

> Strangely enough, despite those failures, the test_harness target still
> reported all tests successful:
> 
> All tests successful (5 subtests UNEXPECTEDLY SUCCEEDED), 63 tests and 323 subtests skipped.
>