Re: [Module::Build] [Fwd: CPAN Upload: J/JP/JPEACOCK/version-0.56_03.tar.gz]

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

On Feb 20, 2006, at 10:10 AM, John Peacock wrote:

> I've released a beta of version.pm to CPAN that includes the  
> following:
>
> 1) code to correctly detect the lack of a working C compiler and  
> install the
> pure Perl module instead (overloading the have_c_compiler sub);

I noticed the subclass just wraps this method in an eval() and  
returns false when the eval() fails.  Has that been a problem?

> I've tested this on Linux and Cygwin using M::B 0.2611 and 0.27_03  
> (my Win32
> machine seems to have forgotten it ever had Perl installed).  I'd  
> really
> appreciate any other testing that people can get for me  
> (specifically where you
> don't have a compiler).

On my OS X machine with perl 5.8.6 and M::B 0.27_03 I get some funny  
output from running 'perl Build.PL':

---------------------------
Creating custom builder _build/lib/version/Builder.pm in _build/lib/ 
version
Checking whether your kit is complete...
Looks good

Checking prerequisites...
Looks good

Checking whether your kit is complete...
Looks good

Checking prerequisites...
Looks good

Creating new 'Build' script for 'version' version '0.56_03'
---------------------------

Looks like that's because you're calling new() twice.  That's to work  
around some problem though, right?

I also get tons of verbose output from 'Build test', do you see that  
too?

---------------------------
t/01base.......ok 1/0# Tests with base class
# tests with bare numbers
# tests with quoted numbers
# tests with stringify
# test illegal formats
t/01base.......ok 10/0# tests with self
# tests with non-objects
t/01base.......ok 28/0# tests with objects
# numeric tests with non-objects
...
---------------------------


  -Ken