But how did this module pass the tests for darwin machines?
Not sure - but it seems there's another bug in File::Repl in that the Makefile.PL fails to specify File::HomeDir as a prerequisite module.
When I try to build File::Repl on Linux, I find that it also tries (and fails) to build and install Win32::API.
But that's not what causes the build to fail - the failure I get (during the "make test" phase) on Linux is:
Running make test
PERL_DL_NONLAZY=1 "/home/sisyphus/perl528-f128/bin/perl" "-Iblib/lib"
+"-Iblib/arch" test.pl
Can't locate File/HomeDir.pm in @INC (you may need to install the File
+::HomeDir module) (@INC contains: blib/lib blib/arch /home/sisyphus/p
+erl528-f128/lib/site_perl/5.28.0/x86_64-linux-quadmath /home/sisyphus
+/perl528-f128/lib/site_perl/5.28.0 /home/sisyphus/perl528-f128/lib/5.
+28.0/x86_64-linux-quadmath /home/sisyphus/perl528-f128/lib/5.28.0 .)
+at test.pl line 9.
BEGIN failed--compilation aborted at test.pl line 9.
Makefile:847: recipe for target 'test_dynamic' failed
make: *** [test_dynamic] Error 2
I can only assume that the smokers already have File::HomeDir installed.
Anyway, if that's the error that's killing you're build, you can get past it by first running "cpan -i File::HomeDir".
Having done all that, I still find on Linux that, although all tests then pass, cpan steadfastly refuses to install the module because of the missing Win32::API module.
Even with force, cpan refuses to install the module - a behaviour that I find offensively annoying.
I don't know how the smokers get around that - maybe they don't have to. Maybe they're just reporting that "make test" was successful (which it was, despite the missing prerequisite).
The fact that the module can't be installed might not bother them as it's beyond their terms of reference ... or something. Dunno.
Anyway, if having reached the stage that cpan refuses to install the module simply because Win32::API was not installed, you should at least be able to cd to that File::Repl build directory and successfully run "make install" (or "sudo make install" if that's applicable).
Cheers,
Rob
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.