From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 717873858D35; Sat, 7 Jan 2023 19:44:51 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 717873858D35 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1673120691; bh=j9QbWlb1ukw6fy66gQyjASoqcoIbPZ6fnnpaKVK3FOo=; h=From:To:Subject:Date:In-Reply-To:References:From; b=M0Zi8zaMgZJNdVyRhlk964MDRIp4YZtPCOls4O02BtWlLLZ1EAB/DWjxoVN9Em3r2 5lqArTDZYw5guwbdESvRoYI6N6Wtp+Q3s9EWM+Wkl52VjJmyskodYRwwI8qLdM6YRk XJzu5FTF5Mvd1C0tMteK4WuGBXk9MqiH19Ie/A2U= From: "euloanty at live dot com" To: gdb-prs@sourceware.org Subject: [Bug build/29966] Cannot build anymore for win32 thread model of gdb Date: Sat, 07 Jan 2023 19:44: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: euloanty at live dot com 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 #8 from cqwrteur --- (In reply to Tom Tromey from comment #7) > (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. >=20 > Previously it didn't work at all and gdb's configure check > correctly detected this and disabled threading. >=20 > These checks no longer seem to be working correctly, as > evidenced by the errors you see. >=20 > To adapt to this change, we need to understand why the configure > checks did not do their job. >=20 > This is why I would like to see your gdbsupport/config.log. > That should contain some clues. The issue is that gdb will set -D_WIN32_WINNT to a lower value than it expe= cts. Then the win32 threading will no longer compile with libstdc++. --=20 You are receiving this mail because: You are on the CC list for the bug.=