Switching to a more recent version of nasm did the trick. As it turns out, before I posted, I had assumed that using nasm might resolve this. However, it appears that I grabbed nasm 2.05 which doesn't support AES-NI instructions, either(?). So, my intial switch to nasm failed with the same errors. After your reply, I upgraded to the latest version, 2.11.8, and it worked. Thanks for reinforcing my assumption and putting me back on track. Regards, Kevin -- -----Original Message----- From: openssl-users [mailto:openssl-users-bounces@xxxxxxxxxxx] On Behalf Of Thomas J. Hruska Sent: Monday, March 23, 2015 9:04 PM To: openssl-users at openssl.org Subject: Re: openssl 1.0.2a vc++ 9 (VS 2008) 64-bit build failing On 3/23/2015 9:51 AM, Kevin Moody wrote: > Hi, > > My apologies if I missed a post about this already, but I'm seeing the following when running `nmake -f ms\ntdll.mak` in the vc9x64 build of openssl 1.0.2a: > > ... > Assembling: tmp32dll\aesni-sha256-x86_64.asm > tmp32dll\aesni-sha256-x86_64.asm(109) : error A2006:undefined symbol : > __imp_Rtl VirtualUnwind > tmp32dll\aesni-sha256-x86_64.asm(127) : error A2006:undefined symbol : > $L$SEH_be gin_aesni_cbc_sha256_enc_xop > tmp32dll\aesni-sha256-x86_64.asm(128) : error A2006:undefined symbol : > $L$SEH_en d_aesni_cbc_sha256_enc_xop > tmp32dll\aesni-sha256-x86_64.asm(129) : error A2006:undefined symbol : > $L$SEH_in fo_aesni_cbc_sha256_enc_xop > tmp32dll\aesni-sha256-x86_64.asm(131) : error A2006:undefined symbol : > $L$SEH_be gin_aesni_cbc_sha256_enc_avx > tmp32dll\aesni-sha256-x86_64.asm(132) : error A2006:undefined symbol : > $L$SEH_en d_aesni_cbc_sha256_enc_avx > tmp32dll\aesni-sha256-x86_64.asm(133) : error A2006:undefined symbol : > $L$SEH_in fo_aesni_cbc_sha256_enc_avx NMAKE : fatal error U1077: > '"c:\Program Files\Microsoft Visual Studio 9.0\VC\BIN > \x86_amd64\ml64.EXE"' : return code '0x1' > Stop. > > What's odd is that this has built in my vc9x32, vc10x32, vc10x64, vc11x32, and vc11x64 build configurations. Just to rule out an environment issue, I built my previous version, 1.0.1g, within this same command prompt. Any ideas or suggestions as to what might be breaking the VS 2008 64-bit build? Has anyone seen this? > > Obviously, I don't know enough about this project to really debug the build much further. So, thanks in advance! > > Regards, > Kevin Use NASM instead of MASM. AES-NI instructions are not supported under the VC++ 2008 compiler. -- Thomas Hruska Shining Light Productions Home of BMP2AVI and Win32 OpenSSL. http://www.slproweb.com/ _______________________________________________ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
