Front page | perl.perl5.porters |
Postings from September 2016
Michiel Beijen wrote: >the issues seem to have to do with the current directory not being in >@INC. It's not that. On one hand, your error message does show "." in @INC as expected. On the other, the module that it couldn't find would never normally be located in the cwd for that process. The module's source is under $perl/cpan/Pod-Simple/lib, which is not in your @INC. During build it gets installed under $perl/lib, which is. So at first glance this looks like a dependency issue. But this could well be Pod-Simple failing to build because of what you show with HTTP-Date: >And this is manually installing a trivial CPAN module on the system >perl (ofc using cpan or cpanm gives similar results): The problem you see here is File::Find failing to recurse into subdirectories. This came up recently on a CPAN-related mailing list. This is probably down to link counts not being reliable on your filesystem, which is to be expected where Windows is involved. That's why the MANIFEST check doesn't see files that patently are actually present, and apparently it also causes module files to not actually be installed. There's a configuration option called "dont_use_nlink" which you need to turn on. That'll suppress the File::Find optimisation that goes awry on your filesystem. This should fix module builds. Make sure you start with a fresh build directory when reconfiguring. -zeframThread Previous | Thread Next