From: Mark Geisert <mark@maxrnd.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: cmake suddenly stopped working
Date: Tue, 17 Nov 2020 14:48:00 -0800 [thread overview]
Message-ID: <2f4aa73e-781e-ba06-f230-4fa884715988@maxrnd.com> (raw)
In-Reply-To: <fa12ed14-46b3-50d8-b02f-814936386328@huarp.harvard.edu>
Norton Allen wrote:
> 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
That exit code usually indicates a missing library at runtime.
> 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?
I'm not seeing it. 'cmake --help' works for me.
Does 'ldd /usr/bin/cmake' give any hint?
..mark
next prev parent reply other threads:[~2020-11-17 22:48 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 [this message]
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=2f4aa73e-781e-ba06-f230-4fa884715988@maxrnd.com \
--to=mark@maxrnd.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).