From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B8E993858C50; Sat, 7 Jan 2023 19:34:16 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B8E993858C50 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1673120056; bh=RXb0ubsWPgG/xbpb4z0HLzaLb9r343ZnKai7I9bEQck=; h=From:To:Subject:Date:In-Reply-To:References:From; b=DE6fGGWUjUnIl+YzMcq/oUhE75O6s2xOtq/IOjaOMontEo/rmc388FnsHQ0hxERJ/ XaIhp710UFQUnOrqugMRt508urt4jlaS6mA4EPgqfdBnV1whM1idq5vfY5WgSnQgOq hBlIhc5HlNZ1hyq6l93fjrEhQa7zWphiP3auWTeI= 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, 07 Jan 2023 19:34:16 +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: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- 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 #7 from Tom Tromey --- (In reply to cqwrteur from comment #6) > (In reply to Tom Tromey from comment #4) > > Can you send gdbsupport/config.log? > > I think that would show what the thread checks are doing. > > gdb's configury is set up to try to adapt to a non-working > > std::thread, so maybe that has stopped working somehow. >=20 > GCC's win32 thread model updates win32 thread. It wasn't working before. Previously it didn't work at all and gdb's configure check correctly detected this and disabled threading. These checks no longer seem to be working correctly, as evidenced by the errors you see. To adapt to this change, we need to understand why the configure checks did not do their job. This is why I would like to see your gdbsupport/config.log. That should contain some clues. --=20 You are receiving this mail because: You are on the CC list for the bug.=