public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Norton Allen <allen@huarp.harvard.edu>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: cmake suddenly stopped working
Date: Tue, 17 Nov 2020 18:21:12 -0500	[thread overview]
Message-ID: <c782735e-ab0c-ab21-d9af-6e6a9a1d674b@huarp.harvard.edu> (raw)
In-Reply-To: <2f4aa73e-781e-ba06-f230-4fa884715988@maxrnd.com>

On 11/17/2020 5:48 PM, Mark Geisert wrote:
> Norton Allen wrote:
>> 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? 

ldd did not complain, but your question reminded me that I should try 
running under strace. That produce the complaint:

    The procedure entry point
    _ZNSt19basic_ostringstreamlcSt11char_traitslcESalcEEC1Ev could not
    be located in the dynamic link library C:\cygwin64\bin\cmake.exe

(I had to type that in, as I could not copy from strace's error dialog.)

That looks like it might be an issue with the g++ library? Any chance 
there was a change in the library that might require a recompile/relink?

I will try rolling that one back.



  reply	other threads:[~2020-11-17 23:21 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 [this message]
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=c782735e-ab0c-ab21-d9af-6e6a9a1d674b@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).