[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: config.guess fails on appveyor
From: |
Earnie |
Subject: |
Re: config.guess fails on appveyor |
Date: |
Wed, 2 May 2018 12:35:54 -0400 |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 |
On 4/27/2018 5:55 PM, Ben Elliston wrote:
> On Fri, Apr 27, 2018 at 12:07:24PM +0200, address@hidden wrote:
>
>> Config.guess fails to detect Cygwin64 on AppVeyor.
>
>>> uname -s = Cygwin64_NT-10.0
>
This doesn't match any Cygwin I've seen. I'm using 64bit Cygwin Windows 10.
$ uname -s
CYGWIN_NT-10.0
$ uname -a
CYGWIN_NT-10.0 MYHOST 2.10.0(0.325/5/3) 2018-02-02 15:16 x86_64 Cygwin
> Hmmm. We only match 'CYGWIN' in all caps:
>
> address@hidden:~/source/config (master)$ grep -i cygwin config.guess
> i*:CYGWIN*:*)
> amd64:CYGWIN*:*:* | x86_64:CYGWIN*:*:*)
>
> Where did this Cygwin come from? Ernie, et al, do we need to match
> "Cygwin", too, now? Sheesh.
>
No. Any foreign build of Cygwin should supply the build parameters
manually. Also follow up on the address@hidden mail list. I've seen
something about AppVeyor on the list but don't remember the details.
--
Earnie
- Re: config.guess fails on appveyor,
Earnie <=