> From: owner-openssl-us...@openssl.org On Behalf Of Pankaj Aggarwal
> Sent: Tuesday, 25 August, 2009 05:06
> I am using cygwin on windows xp to compile FIPS Openssl 1.2 using
Visual studio 2005.
Apparently you mean cygwin _perl_. The MS compiler and linker
(which are the only ones permitted under the validated policy)
run in the normal Windows environment not the Unixoid cygwin one.
> I get the following error after doing ms\do_fips in openssl
directory.
<snip>
> SET FIPS_SHA1_EXE=out32dll\fips_standalone_sha1.exe
<snip>
> perl util\fipslink.pl /nologo /subsystem:console /opt:ref
/dll
> /map /base:0xFB00000 /out:out32dll\libeay32.dll /def:ms/LIBEAY32.def
> @C:\DOCUME~1\PAGGAR~1\LOCALS~1\Temp\nm749.tmp
> sh: out32dllfips_standalone_sha1.exe: command not found
> Invalid hash received for file at util\fipslink.pl line 74.
> NMAKE : fatal error U1077: 'c:\cygwin\bin\perl.EXE' : return code
'0x7f'
It looks like perl's attempt to run the standalone-hash failed
because it used a (cygwin) shell that isn't Windows-aware and
treated the backslash as a shell quote not a pathname character.
There may be some way to configure cygwin perl to behave 'correctly'
for Windows, perhaps by using CMD instead of a Unixoid shell, but
it's probably easier to use perl built for Windows such as ActiveState.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
