From: Dai Conrad <dai.conrad@gmail.com>
To: cygwin mailing list <cygwin@cygwin.com>
Subject: Re: Updated: gcc-7.3.0-2 (x86/x86_64)
Date: Wed, 30 May 2018 20:31:00 -0000 [thread overview]
Message-ID: <CAEotdwmH+KbJqDSQstgAgaFra_gmrxxADY_EaV5GCoT_QeKX5A@mail.gmail.com> (raw)
On Wed, 30 May 2018 11:58 AM, JonY <10walls@gmail.com> wrote:
>
> Does -static change anything?
Interesting! It succeeds with g++ -std=c++17, and does this with
clang++ -std=c++17:
$ clang++ -std=c++17 -static -Wall -Wextra -O2 -o testa testa.cc
/usr/lib/gcc/x86_64-pc-cygwin/7.3.0/libstdc++.a(cow-string-inst.o):cow-string-inst.cc:(.data$_ZNSs4_Rep20_S_empty_rep_storageE[_ZNSs4_Rep20_S_empty_rep_storageE]+0x0):
multiple definition of `std::string::_Rep::_S_empty_rep_storage'
/tmp/testa-c0acb8.o:(.bss[_ZNSs4_Rep20_S_empty_rep_storageE]+0x0):
first defined here
clang-5.0: error: linker command failed with exit code 1 (use -v to
see invocation)
>> #include <shared_mutex>
>
> I'm guessing Cygwin does not support the functionality declared in the
> headers yet.
If that were the case, it should not compile with g++ -std=c++11,
gnu++14, or gnu++17,
but it does. Also, a much cleaner error message could be shown with:
#error shared_mutex not supported
in the header file, instead of lots of "pthread_rwlock_* not declared
in this scope".
(Note: the first one, with the std::stringstream, still fails with -std=gnu++17)
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2018-05-30 16:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 20:31 Dai Conrad [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-30 19:57 Dai Conrad
[not found] <1268fcb1-715a-0518-cc94-91f452d029fb@gmail.com>
2018-05-30 10:57 ` Alberto Escrig Vidal
2018-05-30 16:14 ` JonY
2018-05-31 2:22 ` Ken Brown
2018-06-05 18:07 ` Alberto Escrig Vidal
2018-06-05 23:28 ` JonY
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=CAEotdwmH+KbJqDSQstgAgaFra_gmrxxADY_EaV5GCoT_QeKX5A@mail.gmail.com \
--to=dai.conrad@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).