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

[Ken W. <ke...@ma...>]

On Mar 20, 2006, at 12:18 PM, Andy Dougherty wrote:

> On Mon, 20 Mar 2006, Ken Williams wrote:
>
>>
>> On Mar 20, 2006, at 5:23 AM, Randy W. Sims wrote:
>>>
>>> The update to EU::CBuilder provided only part of the fix. We do  
>>> have a fix
>>> in cvs for the other failures related to Module::Build on BSD.  
>>> There are a
>>> couple of other things that I need to fix: some warnings from  
>>> Archive::Tar,
>>> failures on Windows when using Borland compiler, and I also need  
>>> to check
>>> MinGW on Windows...
>>
>>
>> We probably shouldn't worry too much about Archive::Tar just yet,  
>> it's
>> producing a few failures of its own in blead on OS X, so it's  
>> probably a
>> moving target.
>
> As of today, I'm still getting a number of failures, all of the form
>
> ../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
> ok
>
> What's perhaps equally distressing is that despite these failures,
> t/harness still reports "All tests successful":
>

It's actually telling the truth - all those "failures" are happening  
when it's poking around your disk looking for the right perl  
executable, and sometimes that produces a lot of noise.  It simply  
moves on and eventually finds the right one, and thus eventually  
succeeds.

We've got patches in the pipeline to help a lot with this, but  
they're not applied yet pending some fact-finding about them.

  -Ken