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

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

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.

Or in general: if our @INC is inappropriate to the perls we're  
testing, then we'll see this kind of behavior.  Maybe there's a way  
to short-circuit early?  Compare 'perl -v' before comparing 'Config- 
 >myconfig' perhaps?

  -Ken