How to Compile v10 in Vista 64b ?

iBradleyAllen has asked for the wisdom of the Perl Monks concerning the following question:

Replies are listed 'Best First'.
Re: How to Compile v10 in Vista 64b ? by BrowserUk (Patriarch) on Mar 26, 2010 at 18:29 UTC
4. Well just to try it, did nmake test then nmake install? (in a VS command prompt)and the compiler starts, runs a bit in each case then errors out. What are the errors? Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. "I'd rather go naked than blow up my ass"	[reply]
Re^2: How to Compile v10 in Vista 64b ? by iBradleyAllen (Novice) on Mar 26, 2010 at 18:43 UTC
C:\Users\B\Downloads\latest.tar\latest\perl-5.10.1\win32>"c:\Program Files (x 86)\Microsoft Visual Studio 9.0\Common7\Tools\vsvars32.bat" Setting environment for using Microsoft Visual Studio 2008 x86 tools. C:\Users\B\Downloads\latest.tar\latest\perl-5.10.1\win32>nmake install `Microsoft (R) Program Maintenance Utility Version 9.00.21022.08 Copyright (C) Microsoft Corporation. All rights reserved. link -subsystem:console -out:..\generate_uudmap.exe @C:\Users\ +B\AppDa ta\Local\Temp\nmBA36.tmp LINK : fatal error LNK1181: cannot open input file 'bufferoverflowU.li +b' NMAKE : fatal error U1077: '"c:\Program Files (x86)\Microsoft Visual S +tudio 9.0\ VC\BIN\link.EXE"' : return code '0x49d' Stop.` [download] C:\Users\B\Downloads\latest.tar\latest\perl-5.10.1\win32>nmake test `Microsoft (R) Program Maintenance Utility Version 9.00.21022.08 Copyright (C) Microsoft Corporation. All rights reserved. link -subsystem:console -out:..\generate_uudmap.exe @C:\Users\ +B\AppDa ta\Local\Temp\nmC9A1.tmp LINK : fatal error LNK1181: cannot open input file 'bufferoverflowU.li +b' NMAKE : fatal error U1077: '"c:\Program Files (x86)\Microsoft Visual S +tudio 9.0\ VC\BIN\link.EXE"' : return code '0x49d' Stop.` [download] C:\Users\B\Downloads\latest.tar\latest\perl-5.10.1\win32>nmake makefile Microsoft (R) Program Maintenance Utility Version 9.00.21022.08 Copyright (C) Microsoft Corporation. All rights reserved. 'makefile' is up-to-date C:\Users\B\Downloads\latest.tar\latest\perl-5.10.1\win32>	[reply] [d/l] [select]
Re^3: How to Compile v10 in Vista 64b ? by thunders (Priest) on Mar 26, 2010 at 18:57 UTC
Looks like you have a missing library called "bufferoverflowU". This node has some relevant details and potential solutions.	[reply]
Re^4: How to Compile v10 in Vista 64b ? by iBradleyAllen (Novice) on Mar 26, 2010 at 19:10 UTC
Re^3: How to Compile v10 in Vista 64b ? by BrowserUk (Patriarch) on Mar 26, 2010 at 19:21 UTC
Just comment out the last 3 lines below in the makefile. This was required for earlier versions if the compiler, but not for VC++ v9: `# The 64 bit Platform SDK compilers contain a runtime library that doe +sn't # include the buffer overrun verification code used by the /GS switch. # Since the code links against libraries that are compiled with /GS, t +his # "security cookie verification" must be included via bufferoverlow.li +b. !IF "$(WIN64)" == "define" LIBBASEFILES = $(LIBBASEFILES) bufferoverflowU.lib !ENDIF` [download] A real fix would be to make it conditional upon both platform (64-bit) and compiler CCTYPE. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. "I'd rather go naked than blow up my ass"	[reply] [d/l]
Re^4: How to Compile v10 in Vista 64b ? by iBradleyAllen (Novice) on Mar 26, 2010 at 20:33 UTC
Re^5: How to Compile v10 in Vista 64b ? by BrowserUk (Patriarch) on Mar 26, 2010 at 21:17 UTC
Re^3: How to Compile v10 in Vista 64b ? by iBradleyAllen (Novice) on Mar 26, 2010 at 19:08 UTC
This is what the makefile.mk has in regards to the error # The 64 bit Platform SDK compilers contain a runtime library that doesn't # include the buffer overrun verification code used by the /GS switch. # Since the code links against libraries that are compiled with /GS, this # "security cookie verification" must be included via bufferoverlow.lib. .IF "$(WIN64)" == "define" LIBBASEFILES = $(LIBBASEFILES) bufferoverflowU.lib .ENDIF There was no bufferoverflowU.lib found in the download, will look to download the 64b SDK? "	[reply]
Re^2: How to Compile v10 in Vista 64b ? by Poincare (Initiate) on Mar 28, 2010 at 23:34 UTC
Why not just strawberry perl?	[reply]
Re^3: How to Compile v10 in Vista 64b ? by BrowserUk (Patriarch) on Mar 28, 2010 at 23:37 UTC
Why not just strawberry perl? Why not just what Strawberry Perl? Scrap it? Abandon it? Consign it to the bit bucket? :) I guess you mean, why not use Strawberry Perl. So, let me turn the question around. Why use Strawberry Perl? How would it address the OPs problem? Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. "I'd rather go naked than blow up my ass"	[reply]
Re: How to Compile v10 in Vista 64b ? by syphilis (Archbishop) on Mar 27, 2010 at 08:09 UTC
I'm a bit confused by some things in this thread. Try unpacking the source afresh into a new directory - I'll assume that directory is C:/X. Then 'cd' to C:/X/perl-5.10.1/win32. Since you're (apparently) using a version of MSVC++ that doesn't need or have bufferoverflowU.lib, open the file called 'Makefile' (not 'makefile.mk' - that's for use with 'dmake') and remove (or comment out) the following section of code: `!IF "$(WIN64)" == "define" LIBBASEFILES = $(LIBBASEFILES) bufferoverflowU.lib !ENDIF` [download] If you don't want to install into C:/perl, you'll also want to edit the INST_DRV and/or INST_TOP entries near the beginning of 'Makefile'. Then run 'nmake' (which will use 'Makefile', not 'makefile.mk'). That should set in motion a process that takes about 10 minutes to complete. If it runs to successful completion, it should finish with a message something like `Everything is up to date. 'nmake test' to run test suite`. If it doesn't complete successfully, then we need to see the final error messages. If 'nmake' succeeds, run 'nmake test', then 'nmake install'. (If there are failures running 'nmake test' you might want to defer the running of 'nmake install' until they've been sorted out.) Cheers, Rob	[reply] [d/l] [select]