On Mon, Jul 11, 2011, Tyrel Haveman wrote: > Hello again, > > We've noticed now that while we are able to build the FIPS module for 64-bit > Windows, we cannot for 32-bit Windows. Following these steps: > > set FIPSDIR=..\out > perl Configure VC-WIN32 > ms\do_ms > nmake -f ms\ntdll.mak > > We get this error: > link /nologo /subsystem:console /opt:ref /debug > /out:out32dll\fips_standalone_sha1.exe > @C:\Users\TyrelHa\AppData\Local\Temp\nmC2ED.tmp > sha1dgst.obj : error LNK2019: unresolved external symbol > _fips_sha1_block_data_order referenced in function _fips_sha1_update > out32dll\fips_standalone_sha1.exe : fatal error LNK1120: 1 unresolved > externals > NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio > 10.0\VC\BIN\link.EXE"' : return code '0x460' > Stop. > > I know we should be using do_fips.bat, but it won't let me do a 32-bit build > on a 64-bit platform, so we're using these steps instead. >
The target platform is determined from the environment. Try this before calling do_fips: set PROCESSOR_ARCHITECTURE=x86 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 openssl-dev@openssl.org Automated List Manager majord...@openssl.org
