Welcome to the Monastery | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
From the results so far, it looks as though it's only MS compilers that are producing the failures - yet I have no problem with either MSVC++ 7.0 or Platform SDK for Windows Server 2003 R2.
However, I use each of those compilers only with a perl that was built by that compiler. Lots of people use an MS compiler that did *not* build the perl on which it's being run - eg using MSVC++ 7,8 or 9 with Active Perl (which was built for and by MSVC++ 6.0). IIRC, BrowserUk uses a compiler that's different from the compiler that built his perl ... not sure about cdarke's set up. Lots of times, this doesn't matter, but every now and then it does (because of the mixing of C runtimes that occurs) - and I speculate that this is one of those occasions where it *does* matter. That being so, there's nothing much that Craig can do about it. I guess he could put code in the Makefile.PL that checks that the MSVC++ 6.0 is being used (iff ActivePerl is being used && the compiler is 'cl') - and then abort the build if that's not the case. From memory, Steve Hay did something like that with Win32::SharedFileOpen. Update: In further support of my speculation that the problem comes from mixing MS compilers, I just built Time-Piece-1.16 on ActivePerl using MSVC++ 7.0, and indeed got the failure earlier reported by cdarke, plus one other failure: Yet there's no test failure building Time::Piece with that MSVC++ 7.0 compiler on a perl that was built by MSVC++ 7.0. Cheers, Rob In reply to Re: Testing Time::Piece on Windows/VC
by syphilis
|
|