From: Norton Allen <allen@huarp.harvard.edu>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: cmake suddenly stopped working
Date: Tue, 17 Nov 2020 17:29:03 -0500 [thread overview]
Message-ID: <fa12ed14-46b3-50d8-b02f-814936386328@huarp.harvard.edu> (raw)
Windows 10
Cygwin installed all up to date
cmake 3.17.3-2, which does not appear to have changed since August
Symptoms: cmake fails silently with (or without) any arguments,
including --help. Exit code is 127
I tried to reinstall cmake, the file appears to be identical
cygcheck -s and cygcheck /usr/bin/cmake both look OK to to me, though
I'd be happy to upload if anyone is interested.
My AV is ESET. Tried disabling it to no effect.
This could have been caused by a recent cygwin update. The following
were all installed last Friday. Would anyone like to guess which are
worth checking? I will cross-check with the cygcheck output for cmake.
Is anyone else seeing this? Any suggestions?
Nov 13 11:30 gdb.lst.gz
Nov 13 11:30 git.lst.gz
Nov 13 11:30 gcc-g++.lst.gz
Nov 13 11:30 libsource-highlight4.lst.gz
Nov 13 11:30 openssh.lst.gz
Nov 13 11:29 gcc-core.lst.gz
Nov 13 11:29 libboost_regex1.66.lst.gz
Nov 13 11:29 make.lst.gz
Nov 13 11:29 libfido2.lst.gz
Nov 13 11:29 libsource-highlight-common.lst.gz
Nov 13 11:29 libzstd1.lst.gz
Nov 13 11:29 libisl22.lst.gz
Nov 13 11:29 libicu61.lst.gz
Nov 13 11:29 libguile2.2_1.lst.gz
Nov 13 11:29 libcbor.lst.gz
Nov 13 11:29 libjsoncpp24.lst.gz
Nov 13 11:29 screen.lst.gz
Nov 13 11:29 libncurses-devel.lst.gz
Nov 13 11:29 less.lst.gz
Nov 13 11:29 graphviz.lst.gz
Nov 13 11:29 file.lst.gz
Nov 13 11:29 doxygen.lst.gz
Nov 13 11:29 cygwin-doc.lst.gz
Nov 13 11:29 bzip2.lst.gz
next reply other threads:[~2020-11-17 22:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 22:29 Norton Allen [this message]
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
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=fa12ed14-46b3-50d8-b02f-814936386328@huarp.harvard.edu \
--to=allen@huarp.harvard.edu \
--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).