From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id ED14C3854806; Fri, 13 Jan 2023 19:12:17 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org ED14C3854806
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1673637137;
	bh=YqHKRK0EF6/zRNgDYWw+/JD0xOhe4nx4XUtjN2wgxAI=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=kYA7/Li8oVVhShgWANOMNr6arwnYpBFHC1XrxflQM0grWsii03tXT/5kkz78ZWiWc
	 pVpmFSGeSIrea3dhlNPg5O74VFjTEeej3ypuJao3rShMeMT/uYtNtTMd23VAyjECr7
	 RAOKSJ81TlzdQdJxa3Vnjb8TlRyfwZDYclkRTUkA=
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/29966] Cannot build anymore for win32 thread model of gdb
Date: Fri, 13 Jan 2023 19:12:17 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: build
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tromey at sourceware dot org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: tromey at sourceware dot org
X-Bugzilla-Target-Milestone: 13.1
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-29966-4717-ic74140CbY@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-29966-4717@http.sourceware.org/bugzilla/>
References: <bug-29966-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gdb-prs.sourceware.org>

https://sourceware.org/bugzilla/show_bug.cgi?id=3D29966

--- Comment #38 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to cqwrteur from comment #35)
> (In reply to Tom Tromey from comment #34)
> > We agreed to backport.
> > I think the gdb side of this is done.
>=20
> No this problem is NOT fixed.

If you can think of some change gdb can make that will fix it,
I'm all ears.

My understanding is:

* gdb configure should now correctly detect that threads aren't supported,
but...
* ... there's still a libstdc++ buglet to be addressed in this area

Let me know what you think.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=