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 19:09:05 -0500 [thread overview]
Message-ID: <0c91c91e-70e5-093a-0b61-07b76a52fc4a@huarp.harvard.edu> (raw)
In-Reply-To: <3ccdc37d-953f-f6a5-76af-56e201ee864a@huarp.harvard.edu>
On 11/17/2020 6:48 PM, Norton Allen wrote:
> On 11/17/2020 6:21 PM, Norton Allen wrote:
>> 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.
>
>
> Rolling back to gcc-g++ 9.3.0 did not help.
>
> I did find that entry point string in cmake.exe (all the lowercase
> 'L's I typed in that are actually capital i's. My font makes no
> distinction) and I was able to locate a matching string in
> /lib/gcc/x86_64-pc-cygwin/9.3.0/libstdc++.a, but not in
> libstdc++.dll.a. Running strings on the /usr/bin/cygstdc++-6.dll
> showed the same information. Maybe I need to roll back further!
>
This seems to be the crux of it. That entry point is simply not in the
g++ shared library. I have not figured out why this cropped up today,
since it is not present in the current (10.2.0-1) or previous (9.3.0-2)
versions. I will trying going back to 7.4.0.1, but it's hard to imagine
it's been gone so long and I haven't seen the problem before today.
nort@easwhlpt3425080 /usr/bin
$ strings cygstdc++-6.dll | grep
_ZNSt19basic_ostringstreamIcSt11char_traits
_ZNSt19basic_ostringstreamIcSt11char_traitsIcESaIcEE3strERKSs
_ZNSt19basic_ostringstreamIcSt11char_traitsIcESaIcEE4swapERS3_
_ZNSt19basic_ostringstreamIcSt11char_traitsIcESaIcEEC1EOS3_
_ZNSt19basic_ostringstreamIcSt11char_traitsIcESaIcEEC1ERKSsSt13_Ios_Openmode
_ZNSt19basic_ostringstreamIcSt11char_traitsIcESaIcEEC1ESt13_Ios_Openmode
_ZNSt19basic_ostringstreamIcSt11char_traitsIcESaIcEEC2EOS3_
_ZNSt19basic_ostringstreamIcSt11char_traitsIcESaIcEEC2ERKSsSt13_Ios_Openmode
_ZNSt19basic_ostringstreamIcSt11char_traitsIcESaIcEEC2ESt13_Ios_Openmode
_ZNSt19basic_ostringstreamIcSt11char_traitsIcESaIcEED0Ev
_ZNSt19basic_ostringstreamIcSt11char_traitsIcESaIcEED1Ev
_ZNSt19basic_ostringstreamIcSt11char_traitsIcESaIcEED2Ev
_ZNSt19basic_ostringstreamIcSt11char_traitsIcESaIcEEaSEOS3_
nort@easwhlpt3425080 /usr/bin
$ strings cmake.exe | grep _ZNSt19basic_ostringstreamIcSt11char_traits
_ZNSt19basic_ostringstreamIcSt11char_traitsIcESaIcEEC1Ev
_ZNSt19basic_ostringstreamIcSt11char_traitsIcESaIcEED1Ev
Does this seem like a problem that is likely to be resolved by
rebuilding cmake?
next prev parent reply other threads:[~2020-11-18 0:09 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 [this message]
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=0c91c91e-70e5-093a-0b61-07b76a52fc4a@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).