[openssl.org #4326] Failed to configure for Cygwin-x64

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

[openssl.org #4326] Failed to configure for Cygwin-x64

Rich Salz via RT
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?

Cheers,
Richard

Vid Sun, 21 Feb 2016 kl. 04.33.17, skrev [hidden email]:

> Also see Issue 3110
> (http://rt.openssl.org/Ticket/Display.html?id=3110) and "Adding
> support for x86_64 Cygwin"
> (http://openssl.6102.n7.nabble.com/openssl-org-3110-Adding-support-
> for-x86-64-Cygwin-td46131.html).
>
> The 3110 issue was closed in May 2015, but it looks like something is
> a bit amiss.
>
> > After configuring on Windows 8.1/Core i5 4th gen machine, make'ing
> > depend produces the following errors:
> >
> > $ make depend
> > making depend in crypto...
> > make[1]: Entering directory '/home/Test_User/openssl-1.0.2f/crypto'
> > cc1: error: CPU you selected does not support x86-64 instruction set
> > cc1: error: CPU you selected does not support x86-64 instruction set
> > cc1: error: CPU you selected does not support x86-64 instruction set
> > cc1: error: CPU you selected does not support x86-64 instruction set
> > cc1: error: CPU you selected does not support x86-64 instruction set
> > cc1: error: CPU you selected does not support x86-64 instruction set
> > cc1: error: CPU you selected does not support x86-64 instruction set
> > cc1: error: CPU you selected does not support x86-64 instruction set
> > cc1: error: CPU you selected does not support x86-64 instruction set
> > cc1: error: CPU you selected does not support x86-64 instruction set
> > cc1: error: CPU you selected does not support x86-64 instruction set
> > cc1: error: CPU you selected does not support x86-64 instruction set
> > cc1: error: CPU you selected does not support x86-64 instruction set
> > cc1: error: CPU you selected does not support x86-64 instruction set
> > cc1: error: CPU you selected does not support x86-64 instruction set
> > cc1: error: CPU you selected does not support x86-64 instruction set
> > cc1: error: CPU you selected does not support x86-64 instruction set
> > cc1: error: CPU you selected does not support x86-64 instruction set
> > cc1: error: CPU you selected does not support x86-64 instruction set
> > cc1: error: CPU you selected does not support x86-64 instruction set
> > cc1: error: CPU you selected does not support x86-64 instruction set
> > cc1: error: CPU you selected does not support x86-64 instruction set
> > cc1: error: CPU you selected does not support x86-64 instruction set
> > cc1: error: CPU you selected does not support x86-64 instruction set
> > cc1: error: CPU you selected does not support x86-64 instruction set
> > cc1: error: CPU you selected does not support x86-64 instruction set
> > cc1: error: CPU you selected does not support x86-64 instruction set
> > cc1: error: CPU you selected does not support x86-64 instruction set
> > cc1: error: CPU you selected does not support x86-64 instruction set
> > cc1: error: CPU you selected does not support x86-64 instruction set
> > Makefile:136: recipe for target 'local_depend' failed
> > make[1]: *** [local_depend] Error 1
> > make[1]: Leaving directory '/home/Test_User/openssl-1.0.2f/crypto'
> > Makefile:471: recipe for target 'depend' failed
> > make: *** [depend] Error 1
> >
> > ======================
> >
> > $ ./config shared no-ssl2 no-ssl3 --openssldir="$HOME/ssl"
> > Operating system: x86_64-whatever-cygwin
> > Configuring for Cygwin
> > Configuring for Cygwin
> > no-ec_nistp_64_gcc_128 [default] OPENSSL_NO_EC_NISTP_64_GCC_128
> > (skip dir)
> > no-gmp [default] OPENSSL_NO_GMP (skip dir)
> > no-jpake [experimental] OPENSSL_NO_JPAKE (skip dir)
> > no-krb5 [krb5-flavor not specified] OPENSSL_NO_KRB5
> > no-libunbound [experimental] OPENSSL_NO_LIBUNBOUND (skip dir)
> > no-md2 [default] OPENSSL_NO_MD2 (skip dir)
> > no-rc5 [default] OPENSSL_NO_RC5 (skip dir)
> > no-rfc3779 [default] OPENSSL_NO_RFC3779 (skip dir)
> > no-sctp [default] OPENSSL_NO_SCTP (skip dir)
> > no-ssl-trace [default] OPENSSL_NO_SSL_TRACE (skip dir)
> > no-ssl2 [option] OPENSSL_NO_SSL2 (skip dir)
> > no-ssl3 [option] OPENSSL_NO_SSL3 (skip dir)
> > no-store [experimental] OPENSSL_NO_STORE (skip dir)
> > no-unit-test [default] OPENSSL_NO_UNIT_TEST (skip dir)
> > no-zlib [default]
> > no-zlib-dynamic [default]
> > IsMK1MF=0
> > CC =gcc
> > CFLAG =-D_WINDLL -DOPENSSL_PIC -DOPENSSL_THREADS -DDSO_DLFCN
> > -DHAVE_DLFCN_H -DTERMIOS -DL_ENDIAN -fomit-frame-pointer -O3
> > -march=i486 -Wall -DOPENSSL_BN_ASM_PART_WORDS -DOPENSSL_IA32_SSE2
> > -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM
> > -DSHA512_ASM -DMD5_ASM -DRMD160_ASM -DAES_ASM -DVPAES_ASM
> > -DWHIRLPOOL_ASM -DGHASH_ASM
> > EX_LIBS =
> > CPUID_OBJ =x86cpuid.o
> > BN_ASM =bn-586.o co-586.o x86-mont.o x86-gf2m.o
> > EC_ASM =
> > DES_ENC =des-586.o crypt586.o
> > AES_ENC =aes-586.o vpaes-x86.o aesni-x86.o
> > BF_ENC =bf-586.o
> > CAST_ENC =c_enc.o
> > RC4_ENC =rc4-586.o
> > RC5_ENC =rc5-586.o
> > MD5_OBJ_ASM =md5-586.o
> > SHA1_OBJ_ASM =sha1-586.o sha256-586.o sha512-586.o
> > RMD160_OBJ_ASM=rmd-586.o
> > CMLL_ENC =cmll-x86.o
> > MODES_OBJ =ghash-x86.o
> > ENGINES_OBJ =
> > PROCESSOR =
> > RANLIB =/usr/bin/ranlib.exe
> > ARFLAGS =
> > PERL =/usr/bin/perl.exe
> > THIRTY_TWO_BIT mode
> > DES_PTR used
> > DES_RISC1 used
> > DES_UNROLL used
> > BN_LLONG mode
> > RC4_INDEX mode
> > RC4_CHUNK is undefined
> > e_os2.h => include/openssl/e_os2.h
> > making links in crypto...
> > make[1]: Entering directory '/home/Test_User/openssl-1.0.2f/crypto'
> > ...


--
Richard Levitte
[hidden email]

--
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
Reply | Threaded
Open this post in threaded view
|

Re: [openssl.org #4326] Failed to configure for Cygwin-x64

Rich Salz via RT
On Sun, Feb 21, 2016 at 1:27 AM, Richard Levitte via RT <[hidden email]> 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
Reply | Threaded
Open this post in threaded view
|

Re: [openssl.org #4326] Failed to configure for Cygwin-x64

Jeffrey Walton-3
In reply to this post by Rich Salz via RT
> 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
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Reply | Threaded
Open this post in threaded view
|

Re: [openssl.org #4326] Failed to configure for Cygwin-x64

Rich Salz via RT
> 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
Reply | Threaded
Open this post in threaded view
|

Re: [openssl.org #4326] Failed to configure for Cygwin-x64

Corinna Vinschen
In reply to this post by Rich Salz via RT
On Feb 21 06:27, Richard Levitte via RT 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?

Uh oh, is there a chance that the configury for 1.0.2 is NOT changed
anymore?  We have a set of local patches in the Cygwin distro which
works around the missing pieces in 1.0.2 in a certain way, and changing
the 1.0.2 branch now would break the build scripts for the Cygwin distro.

I would very much prefer if people interested in OpenSSL 1.0.2 for Cygwin
would use the openssl-1.0.2 source archive, which cotains all patches
required for Cygwin, as well as the cygport build script to build openssl
exactly the same way as in the Cygwin distro.

Please let's not break that and stick to the master branch for the
build system changes.


Thanks,
Corinna

--
Corinna Vinschen
Cygwin Maintainer
Red Hat

--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

signature.asc (836 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [openssl.org #4326] Failed to configure for Cygwin-x64

Richard Levitte - VMS Whacker-2
In message <[hidden email]> on Mon, 22 Feb 2016 18:34:04 +0100, Corinna Vinschen <[hidden email]> said:

vinschen> On Feb 21 06:27, Richard Levitte via RT wrote:
vinschen> > I believe that the auto-detecting script, ./config, is lacking detection of
vinschen> > architecture for Cygwin. Does one preferably recognise a x86_64 Cygwin from
vinschen> > `uname -m` or is there something in `uname -s` that should be used as an
vinschen> > indicator?
vinschen>
vinschen> Uh oh, is there a chance that the configury for 1.0.2 is NOT changed
vinschen> anymore?  We have a set of local patches in the Cygwin distro which
vinschen> works around the missing pieces in 1.0.2 in a certain way, and changing
vinschen> the 1.0.2 branch now would break the build scripts for the Cygwin distro.

A patch that fixes ./config was merged to the 1.0.2 branch earlier
today.  Commit 5c57fbb8ca991e8db7ce23174613898a27ca3fcb.  It's a
backport of the corresponding patch in master.  It's a very small
change, I'd be surprised if you can't edit that particular one from
your scripts.

1.0.2 is on long term support, see
http://openssl.org/policies/releasestrat.html.  That means that
reasonable fixes might very well go in.  Sorry if that becomes a
bother.

--
Richard Levitte         [hidden email]
OpenSSL Project         http://www.openssl.org/~levitte/
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Reply | Threaded
Open this post in threaded view
|

Re: [openssl.org #4326] Failed to configure for Cygwin-x64

Corinna Vinschen
On Feb 22 18:43, Richard Levitte wrote:

> In message <[hidden email]> on Mon, 22 Feb 2016 18:34:04 +0100, Corinna Vinschen <[hidden email]> said:
>
> vinschen> On Feb 21 06:27, Richard Levitte via RT wrote:
> vinschen> > I believe that the auto-detecting script, ./config, is lacking detection of
> vinschen> > architecture for Cygwin. Does one preferably recognise a x86_64 Cygwin from
> vinschen> > `uname -m` or is there something in `uname -s` that should be used as an
> vinschen> > indicator?
> vinschen>
> vinschen> Uh oh, is there a chance that the configury for 1.0.2 is NOT changed
> vinschen> anymore?  We have a set of local patches in the Cygwin distro which
> vinschen> works around the missing pieces in 1.0.2 in a certain way, and changing
> vinschen> the 1.0.2 branch now would break the build scripts for the Cygwin distro.
>
> A patch that fixes ./config was merged to the 1.0.2 branch earlier
> today.  Commit 5c57fbb8ca991e8db7ce23174613898a27ca3fcb.  It's a
> backport of the corresponding patch in master.  It's a very small
> change, I'd be surprised if you can't edit that particular one from
> your scripts.
This one's no problem since the build script runs ./Configure directly.

> 1.0.2 is on long term support, see
> http://openssl.org/policies/releasestrat.html.  That means that
> reasonable fixes might very well go in.  Sorry if that becomes a
> bother.

It's not a bother per se, only changes in the build system are
potentially disruptive, that's why I really dread them for the branch.

OTOH, is it much of a problem to apply the patches used for the Cygwin
distro into the 1.0.2 branch so we can get rid of them entirely?  That
would be extremly cool.  I attached them for your review.


Thanks,
Corinna

--
Corinna Vinschen
Cygwin Maintainer
Red Hat

--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

1.0.2-debuginfo.patch (2K) Download Attachment
openssl-1.0.2a-enginesdir.patch (1K) Download Attachment
signature.asc (836 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [openssl.org #4326] Failed to configure for Cygwin-x64

Richard Levitte - VMS Whacker-2
In message <[hidden email]> on Mon, 22 Feb 2016 19:00:08 +0100, Corinna Vinschen <[hidden email]> said:

vinschen> OTOH, is it much of a problem to apply the patches used for the Cygwin
vinschen> distro into the 1.0.2 branch so we can get rid of them entirely?  That
vinschen> would be extremly cool.  I attached them for your review.

I can at least look at them and make a judgement.

--
Richard Levitte         [hidden email]
OpenSSL Project         http://www.openssl.org/~levitte/
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev