public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "i.nixman at autistici dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/108210] error: 'mutex' does not name a type; did you mean 'minutes'? for x86_64-w64-mingw32 target with win32 thread model
Date: Mon, 26 Dec 2022 20:45:17 +0000 [thread overview]
Message-ID: <bug-108210-4-3cIsV7PnMd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108210-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108210
--- Comment #6 from niXman <i.nixman at autistici dot org> ---
(In reply to niXman from comment #5)
> (In reply to niXman from comment #4)
> > (In reply to nightstrike from comment #2)
> > > Is this before or after this patch set was applied?
> > >
> > > https://gcc.gnu.org/pipermail/gcc-patches/2022-December/609116.html
> >
> > I think it can be so because of unspecified `--enable-libstdcxx-threads=yes`
> > option.
>
> will try to build now without that option.
it built successfully.
next prev parent reply other threads:[~2022-12-26 20:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 13:37 [Bug libstdc++/108210] New: " unlvsur at live dot com
2022-12-23 13:40 ` [Bug libstdc++/108210] " unlvsur at live dot com
2022-12-26 15:07 ` nightstrike at gmail dot com
2022-12-26 15:10 ` i.nixman at autistici dot org
2022-12-26 15:12 ` i.nixman at autistici dot org
2022-12-26 15:13 ` i.nixman at autistici dot org
2022-12-26 20:45 ` i.nixman at autistici dot org [this message]
2023-01-04 11:56 ` redi at gcc dot gnu.org
2023-01-04 13:38 ` redi at gcc dot gnu.org
2023-01-04 14:06 ` i.nixman at autistici dot org
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=bug-108210-4-3cIsV7PnMd@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).