[openssl-dev] Fwd: openssl-fips build on cygwin 64bit

Cristi Fati cristifati0 at gmail.com
Thu Jul 20 20:44:42 UTC 2017


Apologies for spam, if this isn't the right place:


*Details*:

   - *cygwin* *64bit*  running on *Win10* (*CYGWIN_NT-10.0 cfati-e5550-0
   2.8.0(0.309/5/3) 2017-04-01 20:47 x86_64 Cygwin*)
   - *openssl-1.0.2l* - irrelevant
   - *openssl-fips-2.0.16* - can be reproduced with previous versions


*make*, after *./config* yields (at the very beginning):

"
*cryptlib.c:1:0: error: CPU you selected does not support x86-64
instruction set*
* /* crypto/cryptlib.c */*
* ^*
*cryptlib.c:1:0: error: CPU you selected does not support x86-64
instruction set*
*make[1]: *** [<builtin>: cryptlib.o] Error 1*
"

That is because in *openssl-fips-2.0.16*'s *Configure* (and *config*
wrapper), 64bit *cygwin* is not handled. After fixing this, everything
builds fine, and (don't mind the paths):

"
*$ ./bin/openssl.exe version -a*
*OpenSSL 1.0.2l-fips  25 May 2017*
*built on:  Thu Jul 20 11:30:16 2017*
*platform: Cygwin-x86_64*
*options:  bn(64,64) rc4(16x,int) des(idx,cisc,16,int) blowfish(idx)*
*compiler: gcc -I. -I.. -I../include  -D_WINDLL -DOPENSSL_PIC
-DOPENSSL_THREADS  -DDSO_DLFCN -DHAVE_DLFCN_H -DTERMIOS -DL_ENDIAN -O3
-Wall -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5
-DOPENSSL_BN_ASM_GF2m
-I/cygdrive/e/Work/Dev/Fati/WinBuild/OPSWopenssl/fips-cyg/fips-build/include
-DRC4_ASM -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM
-DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM*
*OPENSSLDIR:
"/cygdrive/e/Work/Dev/Fati/WinBuild/OPSWopenssl/fips-cyg/build/openssl"*
"

while the last lines of *make test*:
"
*PASS*
*test_bad_dtls*
*../util/shlib_wrap.sh ./bad_dtls_test*
*make[1]: Leaving directory
'/cygdrive/e/Work/Dev/Fati/WinBuild/OPSWopenssl/fips-cyg/openssl-1.0.2l/test'*
"

*Important note*:

   - Since I don't know (I can't say that I tried very hard to find out)
   where the code for *openssl-fips* is on GitHub
   <https://github.com/openssl/openssl> (which branch, or whether it's even
   there), in order to create a pull request, I'm going to use the old way:
   attaching a patch.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mta.openssl.org/pipermail/openssl-dev/attachments/20170720/ea3556b7/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: openssl-fips-2.0.16-cygwin_x86_64.patch
Type: application/octet-stream
Size: 1552 bytes
Desc: not available
URL: <http://mta.openssl.org/pipermail/openssl-dev/attachments/20170720/ea3556b7/attachment.obj>


More information about the openssl-dev mailing list