Thanks Jakob, I'm using MASM (ml and ml64) and it seems to work ok for the 32bit build at least. Should I be using nasm for 64bit instead?
The functionality for SHA512 and the rest seems to be implemented because the test for SHA512 (sha512t.exe) is compiled and works correctly. And I think the symbols are missing from the lib (libeay32.lib) and not from the DLL so I did a grep on SHA512 and I found the following: SHA*_* __imp_SHA*_* However, I found nothing starting with an underscore like ( _SHA512_Update ) while the 32bit build had these symbols as well... any ideas? On Thu, Jan 10, 2013 at 4:23 AM, Jakob Bohm <jb-open...@wisemo.com> wrote: > On 1/9/2013 6:40 PM, Ribhi Kamal wrote: > >> Hi all, >> I've compiled openssl 0.9.8x on windows 7 using VS2010 pro using the >> following steps: >> perl Configure VC-WIN64A --prefix=%LIB_OUT% >> CALL ms\do_win64a >> nmake -f ms\ntdll.mak >> nmake -f ms\ntdll.mak test >> nmake -f ms\ntdll.mak install >> >> Unfortunately the resulting libraries do not have any of the following >> symbols: >> _SHA512_Init >> _SHA512_Update >> _SHA512_Final >> _SHA256_Init >> _SHA256_Update >> _SHA256_Final >> _SHA1_Init >> _SHA1_Update >> _SHA1_Final >> >> On the other hand, the 32bit compilation works fine. Any suggestions on >> what I might be doing wrong. >> >> Please any help would greatly appreciated. >> >> > Did you remember to install NASM? > > Are the functions completely missing or just not exported from the > resulting DLLs? > > > Enjoy > > Jakob > -- > Jakob Bohm, CIO, Partner, WiseMo A/S. http://www.wisemo.com > Transformervej 29, 2730 Herlev, Denmark. Direct +45 31 13 16 10 > This public discussion message is non-binding and may contain errors. > WiseMo - Remote Service Management for PCs, Phones and Embedded > ______________________________**______________________________**__________ > OpenSSL Project http://www.openssl.org > User Support Mailing List openssl-users@openssl.org > Automated List Manager majord...@openssl.org > -- -- Ribhi
