On Wed Jul 10 21:46:50 2013, [email protected] wrote: > I am trying to build the FIPS Object Module for Windows on an AMD64 > machine. I started with the instructions in section 4.3 of the User Guide > 2.0, and was able to build the FIPS module itself, but the instructions for > building a FIPS-capable OpenSSL are specific to 32-bit Windows. I adjusted > the build procedure as follows: > > perl Configure VC-WIN64A fips --with > fipslibdir=..\openssl-fips-2.0.5\out32dll > ms\do_win64a > nmake -f ms\nt.mak > > This seems to work until the linking phase, when I get lots of linking > errors, most of them "unresolved external symbol OPENSSL_cleanse". Sure > enough, there is no mem_clr.obj anywhere. There are a few others as well: > > libeayfips32.lib(cryptlib.obj) : error LNK2019: unresolved external symbol > OPENSSL_ia32_cpuid referenced in function OPENSSL_cpuid_setup > libeayfips32.lib(bn_mont.obj) : error LNK2019: unresolved external symbol > bn_mul_mont referenced in function BN_mod_mul_montgomery
I've just tried this with the latest module and it worked fine. In outline I did this... set FIPSDIR=X:\some\install\path cd <fips_module_dir> ms\do_fips cd <openssl_dir> perl Configure VC-WIN64A fips ms\do_win64a nmake -f ms\nt.mak If you still can't get this to work I'd suggest you ask in openssl-users Steve. -- Dr Stephen N. Henson. OpenSSL project core developer. Commercial tech support now available see: http://www.openssl.org ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [email protected]
