From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 30D813858D28; Sat, 28 Jan 2023 04:00:00 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 30D813858D28 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1674878400; bh=sx0x6DYu9ZKzMGmGr0vPq++Zs5gQaF04qy2LHSsaRXg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Vg0QHZG+Esj2mwD+4+Wg0kwGxHnrme29ZhUIQsCXNPlm2J6hYhRIznxSalR+JV86f LEn9qGbJwENOc/olFpy/0TqlYbcWGCdexyslvj3ipiFr7C8GHnftbRg+7Aw7ENTXHQ DG2sawjkeMIFxfeeF9qb4jp7xj7ZnLR9+zfGQSWQ= 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, 28 Jan 2023 04:00:00 +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: 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 #57 from cqwrteur --- (In reply to cqwrteur from comment #56) > (In reply to cqwrteur from comment #55) > > (In reply to Tom Tromey from comment #53) > > > (In reply to Jonathan Wakely from comment #52) > > > > I think unless OP starts being helpful this should just be closed. = We don't > > > > have enough info to even reproduce the issue. > > >=20 > > > > For that failing build, without the patch in comment 47 > > > > gdbsupport/config.log shows: > > >=20 > > > > So the error is pretty ugly, but gdbsupport/configure correctly det= ects that > > > > std::thread and std::mutex cannot be used when -D_WIN32_WINNT=3D0x0= 501 is used. > > > >=20 > > > > But with or without the patch, libiberty fails when using > > > > -D_WIN32_WINNT=3D0x0501 so OP must be doing something that he's not= showing. > > > > And that's just wasting everybody's time. > > >=20 > > > I tend to agree. > > > OP, can you try an older binutils? > > > Otherwise I plan to close this bug and leave the code as-is. > >=20 > > He is wrong >=20 > https://sourceware.org/bugzilla/show_bug.cgi?id=3D29973 >=20 > I find quite funny why libstdc++ refuses to fix this issue first. jwakely it is all your fault. --=20 You are receiving this mail because: You are on the CC list for the bug.=