You could instal Visual Studio Express, and since you're [presumably] using Windows NT 6.x (in 64-bit mode), the latest version (2013?) should work fine. With that installed, you now have the 64-bit C compiler (cl.exe) available.
Besides, even if you could get it to work without installing Visual Studio, you would end up missing the std. C header files and libc libraries, which are only included with Visual Studio. You could also switch to MinGW or Cygwin and use gcc, but I don't have too much experience with either development environment. Cheers, _RVX -----Original Message----- From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org] On Behalf Of Aaron Bahmer Sent: Monday, April 14, 2014 6:22 PM To: openssl-users@openssl.org Subject: New and bleeding - Install Win64 problems Sorry for the newbie question, but the archives didn't provide me any help. I'm dealing with the heartbleed bug, so updating openssl from 1.0.1e to 1.0.1g on a Windows box where I run Apache/Tomcat. I downloaded the new openssl tarball (albeit with non-matching MD5 signatures) and unpacked it to my server. I then opened the Install.w64 file for guidance. Here's an excerpt where I am working: >>> Compiling procedure ------------------- You will need Perl. You can run under Cygwin or you can download ActiveState Perl from http://www.activestate.com/ActivePerl. You will need Microsoft Platform SDK, available for download at http://www.microsoft.com/msdownload/platformsdk/sdkupdate/. As per April 2005 Platform SDK is equipped with Win64 compilers, as well as assemblers, but it might change in the future. To build for Win64/x64: > perl Configure VC-WIN64A > ms\do_win64a > nmake -f ms\ntdll.mak > cd out32dll > ..\ms\test >>> So, I downloaded and installed ActivePerl and installed the Windows SDK for Win 7 and .NET 4. I had to play with the Windows PATH environment variable a bit to get things to work. The "Configure" command seems to work. The ms\do_win64a has a problem on one line: >> C:\Installers\openssl-1.0.1g>ml64 -c -Foms\uptable.obj ms\uptable.asm >> 'ml64' is not recognized as an internal or external command, >> operable program or batch file. ...but I threw caution to the wind and tried to proceed anyhow. The nmake command is where I crash and burn. It seems to get most of the way through, then chokes out with this error message: >> NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 10.0 >> \VC\bin\cl.EXE"' : return code '0xc0000135' ...in researching this, it sounds like I need to run devenv.exe to work within the VS environment and then execute the cl command. However, having only installed the runtime libraries for VS9 and VS10, I don't have a devenv.exe to run. If I change to the 32bit installation from its instruction file, the nmake command still fails with this same error. Could this still be a path problem? Or??? Thanks. == Aaron Bahmer Director, Instructional Technology Eastern Wyoming College http://ewc.wy.edu | (307) 532-8284 1-866-327-8996 (1-866-EAST WYO) x8284 ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
