However during compilation I get warning about size_t to
int and long conversations: possible loss of data. This is because
size_t and even SOCKET is 64 bit wide in this environment.
Should I care about this?
Not about SOCKET, because even though it's declared a pointer-type, it's
safe to cast it to 32-bit, because it represents an offset in a table
[where it's impossible to exceed the 32-bit limit]. As for rest I was
planning to go through it prior some interim beta...
Or it is enough that tests are all successful.
Formally not [unless you can do is link your app with /largeaddressware:no].
... : error LNK2001: unresolved external symbol OPENSSL_UplinkTable
perl ms/uplink.pl win64a > uplink.asm
ml64 -c uplink.asm
add it to APP_EX_OBJ in ntdll.mak file.
This however was never actually tested, AMD64 part of uplink.pl was
written "blindly." A.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager [EMAIL PROTECTED]
