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.
Any thoughts?
Thanks,
Tyrel
On Thu, Jun 30, 2011 at 4:07 PM, Tyrel Haveman <ty...@binarypeople.net>wrote:
> Ah, okay. We tried that out and the FIPS module does build great
> afterwards. But then, later, the 1.0.1 fips-capable build fails to
> build with this reasoning:
>
> nasm -f win64 -DNEAR -Ox -g -o tmp32dll\rc4-x86_64.obj
> tmp32dll\rc4-x86_
> 64.asm
> tmp32dll\rc4-x86_64.asm:755: error: symbol `L$SEH_begin_RC4_set_key'
> undefined
> tmp32dll\rc4-x86_64.asm:756: error: symbol `L$SEH_end_RC4_set_key'
> undefined
> NMAKE : fatal error U1077: 'C:\devel\crypto\tools\nasm.EXE' : return code
> '0x1'
> Stop.
>
> On Thu, Jun 30, 2011 at 2:28 PM, Dr. Stephen Henson <st...@openssl.org>
> wrote:
> > On Thu, Jun 30, 2011, Tyrel Haveman wrote:
> >
> >> Thanks Steve, but now it's running into this instead:
> >> Assembling: tmp32dll\x86_64cpuid.asm
> >> tmp32dll\x86_64cpuid.asm(9) : error A2008:syntax error : SEGMENT
> >> tmp32dll\x86_64cpuid.asm(12) : error A2008:syntax error : ENDS
> >> NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual
> >> Studio 10.0\VC\BIN\x86_amd64\ml64.EXE"' : return code '0x1'
> >> Stop.
> >>
> >> The code at those lines looks like this:
> >> .data SEGMENT
> >> COMM fips_openssl_ia32cap_p:DWORD:2
> >>
> >> .data ENDS
> >>
> >> I don't know MASM syntax so I'm not sure how to correct this.
> >>
> >
> > You have to use NASM for the build and the build process is simply:
> >
> > ms\do_fips
> >
> > 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
> >
>
