On Sun, Feb 21, 2016 at 1:27 AM, Richard Levitte via RT <r...@openssl.org> wrote: > I believe that the auto-detecting script, ./config, is lacking detection of > architecture for Cygwin. Does one preferably recognise a x86_64 Cygwin from > `uname -m` or is there something in `uname -s` that should be used as an > indicator?
Yes, that seems to be the issue at hand for OpenSSL 1.0.2. Using the following works: $ export KERNEL_BITS=64 $ ./Configure Cygwin-x86_64 ... KERNEL_BITS=64 may not be needed. Its old habit for OS X, where config wants to select 32-bit builds for modern 64-bit machines. Uname (for x86_64 installation): $ uname -m x86_64 $ uname -a CYGWIN_NT-6.3 asus-windows8 2.4.1(0.293/5/3) 2016-01-24 11:26 x86_64 Cygwin $ uname -s CYGWIN_NT-6.3 You can also go to the preprocessor, if interested (for x86_64 installation): $ cpp -dM - </dev/null | egrep -i 'cygwin|x86|amd64|ilp' #define __x86_64 1 #define __amd64 1 #define __CYGWIN__ 1 #define __x86_64__ 1 #define __amd64__ 1 ===== Here are some measurements for Cygwin i686 installed on a 64-bit machine: $ uname -a CYGWIN_NT-6.3-WOW asus-windows8 2.4.1(0.293/5/3) 2016-01-24 11:24 i686 Cygwin $ uname -m i686 $ uname -s CYGWIN_NT-6.3-WOW $ cpp -dM - </dev/null | egrep -i 'cygwin|x86|amd64|ilp' #define _X86_ 1 #define __CYGWIN__ 1 #define __CYGWIN32__ 1 -- Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4326 Please log in as guest with password guest if prompted -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev