From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 6D2BB3858D38; Mon, 26 Dec 2022 20:45:17 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6D2BB3858D38
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1672087517;
	bh=rL8KgAQgEpwYAJhxnPY641KVT/x/IN1hdLL0i4gIRyg=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=lu+3H8QW/pjOEHuOtRJZhE6kJhEYHav7JTxYszdAcGjeMf2S510jO5x7dtsOlZEH1
	 EdLYiEAom830hNPMbblgdjsCG3FtPqoRqOSVkCTj5l0s+EQS4zQjJEf3WkPWitnlit
	 mcYRivMjchzr217Dz1d+zN2NuWY0PRygzH611JVE=
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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: i.nixman at autistici dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-108210-4-3cIsV7PnMd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-108210-4@http.gcc.gnu.org/bugzilla/>
References: <bug-108210-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108210

--- 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?
> > >=20
> > > https://gcc.gnu.org/pipermail/gcc-patches/2022-December/609116.html
> >=20
> > I think it can be so because of unspecified `--enable-libstdcxx-threads=
=3Dyes`
> > option.
>=20
> will try to build now without that option.

it built successfully.=