All the Perl that's Practical to Extract and Report
use Perl Log In
chromatic (983)
(email not shown publicly)
http://wgz.org/chromatic/
So That's a N/A Then?
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.
--Larry Wall in stab.c from the perl source code
No, that's a FAIL (Score:1)
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:
chdir? (Score:1)
So either something is missing from @INC, or something did a chdir unexpectedly?
2 known Module::Build issues (Score:1)
Module::Build->new_from_contextand the commandline invocation ofperl Build.PLproduced differentBuildfiles. The former mangled@INCdifferently than the latter, and sometimes left out additions from afteruse Module::Build.I'm having a bit of trouble finding the ticket in the Module::Build [cpan.org] queue, but it's been resolved some time ago. Of course, the user may not have upgraded yet :(
Also, an unfortunately longstanding, unresolved issue [cpan.org] is that using