From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id CFABD3858D33; Sat, 7 Jan 2023 21:40:04 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CFABD3858D33 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1673127604; bh=dlgiXdaqerazt0nZ72WZ9uJxf9w8FDRN5NXIULiHM4Q=; h=From:To:Subject:Date:In-Reply-To:References:From; b=jaoQupg82T9ntHCHGEihBsIPA9QXib/ePNeael6QvsRrEJsD4BZr7eoNsY79i2X5v k9uye+TMFx6lslZ3DNYTVv4dsSrueTtgkHtxSXxf85IUz8WqGNB8Qqwgk1oADbz1uF WwuLbnOJ/AAJfgcCj/S6vh8krU7IVEYMDbCLPwNY= 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 21:40:04 +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 #11 from cqwrteur --- (In reply to Tom Tromey from comment #9) > (In reply to cqwrteur from comment #8) >=20 > > > This is why I would like to see your gdbsupport/config.log. > > > That should contain some clues. > >=20 > > The issue is that gdb will set -D_WIN32_WINNT to a lower value than it > > expects. Then the win32 threading will no longer compile with libstdc++. >=20 > Last time I tried to bump up _WIN32_WINNT, some users pushed back. > What's the minimum supported by libstdc++? For gdbsupport it seems to be: >=20 > # define _WIN32_WINNT 0x0501 >=20 > Anyway -- can you send the config.log? > We can then arrange to build gdb without threading in this case. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108225 I think this is something also wrong with gcc and libstdc++ too. mutex shou= ld not break if someone defines _WIN32_WINNT macro i think. --=20 You are receiving this mail because: You are on the CC list for the bug.=