Maybe the Test Harness is cocking up my STDOUT file descriptor?I've never managed to understand anything about problems that arise only when Test::Harness is invoked.
(Best news would have been for you to report "Nope - makes no difference" ;-)
perl "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, 'blib\lib', 'blib\arch')" t\00-report-prereqs.t
A shot in the dark - does it make any difference if you remove
undef *Test::Harness::Switches; from that command ?
You mention another build of perl on another system where this problem does not arise.
Do both systems run the same command when 'make test' is run ? (Obviously, they'll invoke different perls.)
Do both systems run the same version of Test::Harness:
perl -MTest::Harness -e "print $Test::Harness::VERSION"
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.