On Thu, Jun 30, 2011, Tyrel Haveman wrote: > We just noticed that building the fips module on Linux works fine with > no-asm, but on a 64-bit Windows build, it doesn't work without no-asm. > Here's the error: > > link /nologo /subsystem:console /opt:ref /debug > /out:out32dll\fips_standalone_sha1.exe > @C:\Users\TyrelHa\AppData\Local\Temp\nmAD0D.tmp > sha1dgst.obj : error LNK2019: unresolved external symbol > fips_sha1_block_data_order referenced in function fips_sha1_update > sha1-x86_64.obj : error LNK2019: unresolved external symbol > OPENSSL_ia32cap_P referenced in function sha1_block_data_order > out32dll\fips_standalone_sha1.exe : fatal error LNK1120: 2 unresolved > externals > NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio > 10.0 > \VC\BIN\x86_amd64\link.EXE"' : return code '0x460' > Stop. > > I don't know enough about the openssl build yet to be able to resolve > this one myself. It works fine if no-asm is specified to Configure. > Can someone take a look? >
Should be fixed in the next snapshot. 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
