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 39E883858D37; Mon, 26 Dec 2022 15:12:47 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 39E883858D37
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1672067567;
	bh=ZFpss1bw/TAeZhVzW/GufTi1INbOS6gIwPW6eYlpZ3s=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=FhtHSUuPQI+8K8aoPA38PG4uvTb2oHwju+PI3S9FdOLu+aBXQu5030FLxatlHqtG5
	 P5M9Aa9Dw1J1Tm7jpp1BjnLGADyT1HMIzKskP28wpku6w3IusJ9ruycOtPZhBG0/ic
	 3sneTgE8a2hDV2nIcMxdGE6y4ePiT6nC9i1dCNIM=
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 15:12:46 +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-qr6TxYYGVK@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 #4 from niXman <i.nixman at autistici dot org> ---
(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

I think it can be so because of unspecified `--enable-libstdcxx-threads=3Dy=
es`
option.=