public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: cmake suddenly stopped working
Date: Wed, 18 Nov 2020 16:33:18 +0100	[thread overview]
Message-ID: <ad902a4f-2f70-a114-f1fc-c331fa9112fa@gmail.com> (raw)
In-Reply-To: <8b5c7352-0a0e-1931-fe8b-741acce9d576@huarp.harvard.edu>

On 18.11.2020 14:54, Norton Allen wrote:
> On 11/18/2020 6:31 AM, Marco Atzeri via Cygwin wrote:
>> 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" ?
> 
> I rolled back forward to 3.17.3-2 and verified that 3.17.3-2 still shows 
> the problem:
> 
> $ cygcheck cmake
> Found: C:\cygwin64\bin\cmake.exe

>        C:\Program 
> Files\OpenJDK\jdk-13\bin\api-ms-win-core-rtlsupport-l1-1-0.dll

this is strange

Can you try also
    strace -o cmake.out /usr/bin/cmake --version

I expect an error with a specific shared library

  reply	other threads:[~2020-11-18 15:33 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
2020-11-18 13:54             ` Norton Allen
2020-11-18 15:33               ` Marco Atzeri [this message]
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=ad902a4f-2f70-a114-f1fc-c331fa9112fa@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).