In message <20160222180008.ga31...@calimero.vinschen.de> on Mon, 22 Feb 2016
19:00:08 +0100, Corinna Vinschen 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?
On Feb 22 18:43, Richard Levitte wrote:
> In message <20160222173404.gb11...@calimero.vinschen.de> on Mon, 22 Feb 2016
> 18:34:04 +0100, Corinna Vinschen said:
>
> vinschen> On Feb 21 06:27, Richard Levitte via RT wrote:
> vinschen> > I believe that the auto-detecting
In message <20160222173404.gb11...@calimero.vinschen.de> on Mon, 22 Feb 2016
18:34:04 +0100, Corinna Vinschen 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> >
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,
#4326] Failed to configure for
Cygwin-x64
It failed to 'make test' at d784bcffa3dcd7ac4a0c77bfac4e686dcb771bd9 this
morning.
Test Summary Report
---
../../openssl/test/recipes/70-test_sslcertstatus.t (Wstat: 28416 Tests: 0
Failed: 0)
Non-zero exit status: 111
Parse errors: Bad
#4326] Failed to configure for
Cygwin-x64
It failed to 'make test' at d784bcffa3dcd7ac4a0c77bfac4e686dcb771bd9 this
morning.
Test Summary Report
---
../../openssl/test/recipes/70-test_sslcertstatus.t (Wstat: 28416 Tests: 0
Failed: 0)
Non-zero exit status: 111
Parse errors: Bad
It failed to 'make test' at d784bcffa3dcd7ac4a0c77bfac4e686dcb771bd9 this
morning.
Test Summary Report
---
../../openssl/test/recipes/70-test_sslcertstatus.t (Wstat: 28416 Tests: 0
Failed: 0)
Non-zero exit status: 111
Parse errors: Bad plan. You planned 1 tests but ran 0.
It failed to 'make test' at d784bcffa3dcd7ac4a0c77bfac4e686dcb771bd9 this
morning.
Test Summary Report
---
../../openssl/test/recipes/70-test_sslcertstatus.t (Wstat: 28416 Tests: 0
Failed: 0)
Non-zero exit status: 111
Parse errors: Bad plan. You planned 1 tests but ran 0.
On Sun, Feb 21, 2016 at 2:50 AM, Richard Levitte via RT
wrote:
> Would you try the attached patch, please?
>
Looks good for both 1.0.2 and Master.
Its also nice to see CHACHA_ENC and POLY1305_OBJ in the list below.
=
openssl-git $ ./config
Operating system:
On Sun, Feb 21, 2016 at 2:50 AM, Richard Levitte via RT
wrote:
> Would you try the attached patch, please?
>
Looks good for both 1.0.2 and Master.
Its also nice to see CHACHA_ENC and POLY1305_OBJ in the list below.
=
openssl-git $ ./config
Operating system:
> 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
> 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
On Sun, Feb 21, 2016 at 1:27 AM, 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
13 matches
Mail list logo