[openssl-dev] [openssl.org #4042] Build Bug w/ OpenSSL on Windows? No Applink

[Stephen Henson via RT]

On Tue Sep 15 14:33:33 2015, cberube at us.ibm.com wrote:
> Hi,
>
> I'm trying to build the FIPS-140 compliant OpenSSL software on my
> Windows 7
> system using the Visual Studio 2015 compiler. I am using OpenSSL-FIPS-
> 2.0.10
> and OpenSSL-1.0.2d. I'm getting the following build error when trying
> to build
> the 32-bit version of the OpenSSL libraries:
>
> link /nologo /subsystem:console /opt:ref /debug /dll /fixed /map
> /base:0xFB00000
> /out:out32dll\libeay32.dll /def:ms/LIBEAY32.def
> @C:\Users\username\AppData\Local
> \Temp\nm8E.tmp
> Creating library out32dll\libeay32.lib and object
> out32dll\libeay32.exp
> out32dll\fips_premain_dso.exe out32dll\libeay32.dll
> OPENSSL_Uplink(01489000,08): no OPENSSL_Applink
> Get hash failure at \usr\local\ssl\fips-2.0\bin\fipslink.pl line 60.
> NMAKE : fatal error U1077: 'C:\Perl64\bin\perl.EXE' : return code
> '0x1'
> Stop.
>
> Here's how I went about building it:
>
> 0) Executed "C:\Program Files (x86)\Microsoft Visual Studio
> 14.0\VC\bin\vcvars32.bat" in a DOS command prompt window.
> 1) Extracted the files for OpenSSL-FIPS-2.0.10
> 2) cd OpenSSL-FIPS-2.0.10
> 3) Perl Configure VC-WIN32 no-asm fipscheck no-idea no-mdc2 no-rc5
> 4) ms\do_ms
> 5) nmake -f ms\ntdll.mak
> 6) nmake -f ms\ntdll.mak install

You cannot use custom commands when building the FIPS module or the result is
not compliant. You have to do:

ms\do_fips

Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org