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

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

Andy Dougherty wrote:
> On Mon, 13 Mar 2006, Ken Williams wrote:
> 
> 
>>On Mar 13, 2006, at 8:02 PM, Randy W. Sims wrote:
>>
>>
>>>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.
>>
>>I have a little theory that in some cases it's actually the reverse - our @INC
>>is set to find modules in the not-yet-installed perl (otherwise no modules
>>would be able to load, and they do load), but we're testing out other perls
>>and *they* can't find an appropriate Config.pm.
> 
> 
> Yes, in some cases it's the reverse.  In the first error message I posted, 
> it's the just-built perl that's complaining.  In the second error message, 
> it's an old perl5.00503.  
> 
> I'm happy to report that in both cases, however, Randy's patch works!
> 
> Thanks!
> 

Attached are my final suggested patches for MB & EUCB.

Note that I've restricted the search for the perl interpreter so that it 
does not search in the PATH if PERL_CORE is set as I believe this is 
more correct. In practice this has no effect on any system I've tested 
on because we always find it where we expect now.

Also, find_perl_interpreter now throws an exception if it fails.

If this is sensible I can check it in and generate a patch for blead.

Randy.