Re: perl 5.16.0 build is failing on windows x64

Interesting ... the OP is using VC10 (presumably an x64 build thereof).
Does anyone here use VC10 to build an x64 perl ?
Does anyone anywhere use *any* version of VC to build an x64 perl ?
ActiveState (still, afaik) don't - they use the Platform SDK compiler, which builds x64 perl-5.16.0 just fine.

Cheers,
Rob

Comment on Re: perl 5.16.0 build is failing on windows x64

Replies are listed 'Best First'.
Re^2: perl 5.16.0 build is failing on windows x64 by bulk88 (Priest) on Sep 22, 2012 at 04:04 UTC
VS 2008 generates a x64 Perl without any issues for me. VS 2003 also generates a 32 bit Perl without any issues for me. You know that VC 10 is also a synonym for Visual C++ 4.0 ? ;-) edit: if you didn't understand the jk, _MSC_VER == 1000 is Visual C 4. So VC 4's official name is "Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 10.00.5270 for 80x86" which abbreviates to "MS C V10" or "MS C 10", which is fudged to "VC 10". Realistically, in 2012, you can bet VC 10 means VC 2010. Also AS uses a Platform SDK for x64 that was released between 2003 and 2005. This is because until VS 2005 was released x64 Platform SDK linked with x64 msvcrt.dll not a VS version specific CRT. The C compiler included in the DDK, if used to compile usermode code, will still compile with msvcrt.dll and not a VS specific DLL. AS has a policy for AP to only use msvcrt.dll. Google for more info.	[reply]
Re^3: perl 5.16.0 build is failing on windows x64 by syphilis (Archbishop) on Sep 22, 2012 at 04:21 UTC
You know that VC 10 is also a synonym for Visual C++ 4.0 ? No - I didn't know that. Actually, I got the "10" from "VStudio10" (on his scratchpad) ... which doesn't really prove anything at all about which version the OP is using. Cheers, Rob	[reply]