Rob - apologies for the late reply.

A shot in the dark - does it make any difference if you remove undef *Test::Harness::Switches; from that command ?

Removing undef *Test::Harness::Switches; from the command results in much the same - see error below:

>perl "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "test_harness(0
+, 'blib\lib',
'blib\arch')" t\00-report-prereqs.t
t\00-report-prereqs.t .. Can't dup STDOUT:  Bad file descriptor at C:/
+perl-5.20.3/lib/Test/Builder.pm line 1952.
Compilation failed in require at C:/perl-5.20.3/lib/Test/Builder/Modul
+e.pm line 5.
BEGIN failed--compilation aborted at C:/perl-5.20.3/lib/Test/Builder/M
+odule.pm line 5.
Compilation failed in require at C:/perl-5.20.3/lib/Test/More.pm line 
+23.
BEGIN failed--compilation aborted at C:/perl-5.20.3/lib/Test/More.pm l
+ine 23.
Compilation failed in require at t\00-report-prereqs.t line 8.
BEGIN failed--compilation aborted at t\00-report-prereqs.t line 8.
t\00-report-prereqs.t .. Dubious, test returned 9 (wstat 2304, 0x900)
No subtests run

Test Summary Report
-------------------
t\00-report-prereqs.t (Wstat: 2304 Tests: 0 Failed: 0)
  Non-zero exit status: 9
  Parse errors: No plan found in TAP output
Files=1, Tests=0,  1 wallclock secs ( 0.05 usr +  0.05 sys =  0.09 CPU
+)
Result: FAIL
Failed 1/1 test programs. 0/0 subtests failed.

[download]

System 2 - where the problem isn't evident

Test::Harness Version info on both systems

System 1 (Win7 machine running perl-5.20.3 compiled with VC2015 RC2)

>perl -MTest::Harness -e "print $Test::Harness::VERSION"
3.30

[download]

System 2 (Win10 machine running perl-5.20.3 compiled with VC2015 RC2)

>perl -MTest::Harness -e "print $Test::Harness::VERSION"
3.30

[download]

It's quite bizarre and I'm out of ideas as to why my STDOUT file descriptor is evidently corrupt on the Win7 machine.

In reply to Re^4: Bad file descriptor error in Win32 VC2015 compiled perl-5.20.3 by shadowsong
in thread Bad file descriptor error in Win32 VC2015 compiled perl-5.20.3 by shadowsong

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.