From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 729553858C3A; Sat, 14 Jan 2023 17:11:52 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 729553858C3A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1673716312; bh=L18npkxlnkuef8+J/lEBWIuEOz077Y8YqWS3ZYPQmYM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=c0gevpp21ltlh5BK6fZY6vvFR94Rg4KDtrz+k4Bi1Pchb7bW9sjcx3v7HwYVjf7Aq LQvOlbCUB6CwrnqzZybQJ7Ffuc75OQKkKpWjKEKZIO6PEB7pvO4xtjJI8Xn2op9/FO sTWiF5iBulCy+PI5Zk6qzFwFfROC9PZWi/0P6UJI= From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug build/29966] Cannot build anymore for win32 thread model of gdb Date: Sat, 14 Jan 2023 17:11:51 +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: In-Reply-To: References: 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: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29966 --- Comment #44 from Tom Tromey --- (In reply to Joel Brobecker from comment #43) > Maybe I'll amend: >=20 > Does it impact people trying to build a recent GDB using a recent GCC on = old > versions of Windows (versions that would be older than Windows Vista)? Yes, but the IIUC there is an additional fix in upstream libstdc++ that is planned to be fixed. So it affects a small segment of users at present: people building gdb on an old windows with a gcc from git. (That's my understanding anyway) I tend to think this bug can be closed again. (In reply to cqwrteur from comment #41) > You can detect include with __GTHREAD_HAS_COND macro I'd rather gdb not rely on libstdc++ internals. --=20 You are receiving this mail because: You are on the CC list for the bug.=