Hi, I've stumbled over two problems with building the OpenSSL engine 0.9.6a for Windows-NT: 1) It automatically adds the advapi32-library to the libs. While this is probably fine when building a DLL, you'll get problems (dupliate symbols) when using a statically linked OpenSSL. Fix: remove it from the perl script in util/pl/VC_32.pl: 115c115 < $ex =' '; --- > $ex =' advapi32.lib'; 2) the file crypto/bio/b_print.c has a too naive view about the availability of 64-bit integral data types. It first has the rather good idea of letting bn.h decide whether 64-bit longs are supported (line 75), but if BN_LLONG is defined, it automatically assumes that "long long" is the correct type instead of special-casing for NT's __int64 (yuck!) like bn.h does. I don't know whether b_print.c actually needs the type to be signed, but if an unsigned will do, I'd suggest simply using the BN_ULLONG type. Anyone knows this ? If b_print.c insists on having a signed data type, what about not just defining BN_LLONG without a value, but with the value "long long" or, in the case of NT, with "__int64", so that b_print.c can use that one. Would there be any side effects ? Anyway it'd be nice if these problems would be fixed in an upcoming release... :-) cheers, Wolfgang -- ==================================================================== Wolfgang Bachmann E-Mail: [EMAIL PROTECTED] ZOSO Forschungsges.m.b.H. Phone: (++43) 3127 20900 Friesachstrasse 15 Fax: (++43) 3127 20900-24 A-8114 Stuebing - Austria http://www.zoso.at ==================================================================== ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
