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 <[email protected]> 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 [email protected]
> Automated List Manager [email protected]
>
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [email protected]
Automated List Manager [email protected]
