From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 37B013854806; Fri, 13 Jan 2023 19:14:47 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 37B013854806 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1673637287; bh=74nc8KOkx2I5tqjkaORCs/E9YytYRZQTP1EjU9p00So=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Js4qgspD1ndU4sjsXS2T9OGt5rhtUjEOaJl+api9kZq6RCe79WzE2bXXnXXQkhc9A yHtcicJxUecg1cR2xpyWLI6rIWd02t52xFU19U0NmruU5CYLqeoKU1CEkxqMlKdsqY HXW2MiIsEdbu5yJd2mvZYTzGfC5LXAv0ejUL1f7A= 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: Fri, 13 Jan 2023 19:14:46 +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: 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 #39 from cqwrteur --- Yes. I think =E2=80=9Cgdb configure should now correctly detect that thread= s aren't supported=E2=80=9D Because libstdc++ clearly does not want to fix the problem. Sent from Mail for Windows From: tromey at sourceware dot org Sent: Friday, January 13, 2023 14:12 To: euloanty@live.com Subject: [Bug build/29966] Cannot build anymore for win32 thread model of g= db https://sourceware.org/bugzilla/show_bug.cgi?id=3D29966 --- Comment #38 from Tom Tromey --- (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. > > 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. -- You are receiving this mail because: You reported the bug. You are on the CC list for the bug. --=20 You are receiving this mail because: You are on the CC list for the bug.=