Re^4: Bad file descriptor error in Win32 VC2015 compiled perl-5.20.3

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

Yes - both systems run the same command when make test is run
Yes - both systems run the same version of Test::Harness

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.

Comment on Re^4: Bad file descriptor error in Win32 VC2015 compiled perl-5.20.3 Select or Download Code

Replies are listed 'Best First'.
Re^5: Bad file descriptor error in Win32 VC2015 compiled perl-5.20.3 by syphilis (Archbishop) on Mar 27, 2016 at 00:01 UTC
I'm out of ideas as to why my STDOUT file descriptor is evidently corrupt on the Win7 machine Same here. It would be interesting to know whether the same problem exists when perl-5.20.3 is built with gcc. If you think that's worth investigating you could install 32-bit and/or 64-bit StrawberryPerl portable builds of 5.20.3 and see how they handle the installation of Path::Tiny. You could also try a more recent version of perl. But whether any of that would lead to enlightenment is anyone's guess ;-) On my Windows7 machine, I have 64-bit perl-5.18.0 built with "Microsoft (R) C/C++ Optimizing Compiler Version 14.00.40310.41 for AMD64" - which is a different version of perl built using a different Microsoft Compiler. FWIW (not much) Path::Tiny builds fine on that build of perl. Cheers, Rob	[reply]
Re^6: Bad file descriptor error in Win32 VC2015 compiled perl-5.20.3 by shadowsong (Pilgrim) on Mar 30, 2016 at 10:44 UTC
Rob, Thanks for all your help. The idea was to go with perl-5.20.x as that was the latest version of perl that works with mod_perl v2.0.9. The problem I was having wasn't just limited to Path::Tiny, but any module I attempted to install via `cpan` would fail with that `Bad File Descriptor` error. After much grief I got fed up and compiled it using VC2010. It now works as expected and I can install modules hassle free. If I had to put money on it - I would say it was down the patches applied to perlio.c et al; in order to get it to compile with VC2015... Cheers, Shadowsong	[reply] [d/l] [select]


Clear questions and runnable code get the best and fastest answer
	PerlMonks