From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: cmake suddenly stopped working
Date: Wed, 18 Nov 2020 12:31:34 +0100 [thread overview]
Message-ID: <ecf6ce39-0278-a513-942b-6affbb04d9f0@gmail.com> (raw)
In-Reply-To: <cc0cdbb1-472e-c0d8-49b4-06d3b6510304@huarp.harvard.edu>
On 18.11.2020 01:24, Norton Allen wrote:
> Rolling back cmake from 3.17.3-2 to 3.14.5-1 seems to have resolved the
> problem.
>
> Any idea why no one else seems to be seeing this problem with 3.17.3-2?
>
I assume you had an incomplete upgrade.
what is the output of "cygcheck cmake" ?
$ cygcheck cmake
Found: D:\cygwin64\bin\cmake.exe
D:\cygwin64\bin\cmake.exe
D:\cygwin64\bin\cygwin1.dll
C:\WINDOWS\system32\KERNEL32.dll
C:\WINDOWS\system32\ntdll.dll
C:\WINDOWS\system32\KERNELBASE.dll
D:\cygwin64\bin\cyggcc_s-seh-1.dll
D:\cygwin64\bin\cygstdc++-6.dll
D:\cygwin64\bin\cygarchive-13.dll
D:\cygwin64\bin\cygbz2-1.dll
D:\cygwin64\bin\cygcrypto-1.1.dll
D:\cygwin64\bin\cygz.dll
D:\cygwin64\bin\cygiconv-2.dll
D:\cygwin64\bin\cyglz4-1.dll
D:\cygwin64\bin\cyglzma-5.dll
D:\cygwin64\bin\cyglzo2-2.dll
D:\cygwin64\bin\cygxml2-2.dll
D:\cygwin64\bin\cygzstd-1.dll
D:\cygwin64\bin\cygcurl-4.dll
D:\cygwin64\bin\cygbrotlidec-1.dll
D:\cygwin64\bin\cygbrotlicommon-1.dll
D:\cygwin64\bin\cyggssapi_krb5-2.dll
D:\cygwin64\bin\cygk5crypto-3.dll
D:\cygwin64\bin\cygkrb5support-0.dll
D:\cygwin64\bin\cygintl-8.dll
D:\cygwin64\bin\cygkrb5-3.dll
D:\cygwin64\bin\cygcom_err-2.dll
D:\cygwin64\bin\cygidn2-0.dll
D:\cygwin64\bin\cygunistring-2.dll
D:\cygwin64\bin\cyglber-2-4-2.dll
D:\cygwin64\bin\cygldap-2-4-2.dll
D:\cygwin64\bin\cygsasl2-3.dll
D:\cygwin64\bin\cygssl-1.1.dll
D:\cygwin64\bin\cygnghttp2-14.dll
D:\cygwin64\bin\cygpsl-5.dll
D:\cygwin64\bin\cygssh2-1.dll
D:\cygwin64\bin\cygcrypto-1.0.0.dll
D:\cygwin64\bin\cygjsoncpp-24.dll
D:\cygwin64\bin\cygrhash-0.dll
D:\cygwin64\bin\cyguv-1.dll
next prev parent reply other threads:[~2020-11-18 11:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 22:29 Norton Allen
2020-11-17 22:48 ` Mark Geisert
2020-11-17 23:21 ` Norton Allen
2020-11-17 23:48 ` Norton Allen
2020-11-18 0:09 ` Norton Allen
2020-11-18 0:24 ` Norton Allen
2020-11-18 10:40 ` Lemures Lemniscati
2020-11-18 14:03 ` Norton Allen
2020-11-18 11:31 ` Marco Atzeri [this message]
2020-11-18 13:54 ` Norton Allen
2020-11-18 15:33 ` Marco Atzeri
2020-11-18 16:09 ` Norton Allen
2020-11-18 16:35 ` Marco Atzeri
2020-11-18 18:29 ` Norton Allen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ecf6ce39-0278-a513-942b-6affbb04d9f0@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).