>From: owner-openssl-us...@openssl.org On Behalf Of Ribhi Kamal
>Sent: Thursday, 10 January, 2013 17:51
>Never mind, the application (virtualbox) was incorrectly trying to use
>the 32bit version of openssl. But I still don't understand why a 32bit
>version has different symbols that the 64bit one.
Winx86 has two generally used calling conventions,
which are distinguished by different name mangling:
cdecl has underscore at the beginning;
stdcall has atsign-number (of bytes popped) at the end.
(Plus several more that are used more locally.)
(I've been told) Winx64 has only one calling convention
and doesn't need this mangling, so maybe it isn't done
or at least isn't done the same way.
>On Thu, Jan 10, 2013 at 12:01 PM, Ribhi Kamal <rbhka...@gmail.com> wrote:
> 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?
INSTALL.W64 says asm is not supported, and ms/do_win64a.bat
does mk1mf no-asm. So assembler shouldn't matter.
<snip rest>
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
