I'm really not sure what to do with a CPANPLUS failure report for P5NCI:
... [MSG] [Sat Jul 28 18:04:16 2007] Extracted 'P5NCI-0.30/build_lib/' [MSG] [Sat Jul 28 18:04:16 2007] Extracted 'P5NCI-0.30/build_lib/P5NCI/' [MSG] [Sat Jul 28 18:04:16 2007] Extracted 'P5NCI-0.30/build_lib/P5NCI/GenerateXS.pm' ... [ERROR] [Sat Jul 28 18:04:17 2007] Could not run 'Build': Can't locate P5NCI/GenerateXS.pm in @INC (@INC contains: /home/mauke/usr/local/lib/perl5/5.8.8/i686-linux-64int-ld /home/mauke/usr/local/lib/perl5/5.8.8 /home/mauke/usr/local/lib/perl5/site_perl/5.8.8/i686-linux-64int-ld /home/mauke/usr/local/lib/perl5/site_perl/5.8.8 /home/mauke/usr/local/lib/perl5/site_perl .) at build_lib/P5NCI/Build.pm line 53.
In other words, my Build.PL
successfully loaded P5NCI::Build
from the build_lib/ directory, but then it couldn't load P5NCI::GenerateXS
, which is in the same directory as P5NCI::Build
.
I find that difficult to believe.
According to Barbie and some documentation lost in the mists, "NA" represents "Not Available" -- meaning that the OS or Perl version are not supported.
This is a build failure -- it might be a problem with the toolchain, but it's a build failure all the same.
And it's definitely weird. I can't see why 'build_lib' wouldn't be added to @INC in the Build file.
As a side note, trying P5NCI on my system gives me another odd error:
Use of uninitialized value in numeric lt (<) at build_lib/P5NCI/Build.pm line 43.
Can't write lib/P5NCI.xs: Permission denied
Hopefully, I'll soon have CPAN+CPAN::Reporter reporting PL and make/Build failures as well so you'll get a better fail report from CPAN, too.
Module::Build->new_from_context
and the commandline invocation of perl Build.PL
produced different Build
files. The former
mangled @INC
differently than the latter, and sometimes left out additions from after use Module::Build
.
I'm having a bit of trouble finding the ticket in the Module::Build queue, but it's been resolved some time ago. Of course, the user may not have upgraded yet
Also, an unfortunately longstanding, unresolved issue is that using the Module::Build API, one can't get to the errors/output reported during the build stages, so the test report doesn't show you enough diagnostics to remedy the problem.
Hopefully this sheds some light on the situation.