public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/29966] Cannot build anymore for win32 thread model of gdb
Date: Tue, 10 Jan 2023 01:32:26 +0000	[thread overview]
Message-ID: <bug-29966-4717-ZcLgfvZd4l@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29966-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29966

--- Comment #22 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to cqwrteur from comment #20)
> (In reply to Tom Tromey from comment #19)
> > Could you please try this patch?
> > 
> > https://sourceware.org/pipermail/gdb-patches/2023-January/195484.html
> 
> #if _WIN32_WINNT >= 0x0600
> #define __GTHREAD_HAS_COND 1
> #define __GTHREADS_CXX0X 1
> #endif
> 
> So the variable needs to be larger than 0x0600

Let me agree here with Jonathan.
The goal of the patch is not to somehow make threads work on
your system.  That can't be done by gdb configure.
The goal is to correctly detect the problem and disable
threading support in gdb.

Did you try the patch?
If so, please report the (presumably new) problem.
If not, please apply it and do a clean build.
Thanks.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-01-10  1:32 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-06  0:14 [Bug build/29966] New: " euloanty at live dot com
2023-01-06 13:41 ` [Bug build/29966] " tromey at sourceware dot org
2023-01-07  0:53 ` euloanty at live dot com
2023-01-07  0:54 ` euloanty at live dot com
2023-01-07  3:41 ` tromey at sourceware dot org
2023-01-07  3:42 ` tromey at sourceware dot org
2023-01-07 18:14 ` euloanty at live dot com
2023-01-07 19:34 ` tromey at sourceware dot org
2023-01-07 19:44 ` euloanty at live dot com
2023-01-07 20:07 ` tromey at sourceware dot org
2023-01-07 21:13 ` euloanty at live dot com
2023-01-07 21:40 ` euloanty at live dot com
2023-01-07 21:58 ` jwakely.gcc at gmail dot com
2023-01-07 22:00 ` euloanty at live dot com
2023-01-07 22:04 ` jwakely.gcc at gmail dot com
2023-01-07 22:05 ` jwakely.gcc at gmail dot com
2023-01-07 22:08 ` jwakely.gcc at gmail dot com
2023-01-07 22:13 ` jwakely.gcc at gmail dot com
2023-01-08  1:16 ` tromey at sourceware dot org
2023-01-08  4:06 ` tromey at sourceware dot org
2023-01-09 14:48 ` tromey at sourceware dot org
2023-01-10  0:15 ` euloanty at live dot com
2023-01-10  0:45 ` jwakely.gcc at gmail dot com
2023-01-10  1:32 ` tromey at sourceware dot org [this message]
2023-01-10  6:57 ` euloanty at live dot com
2023-01-10 11:47 ` jwakely.gcc at gmail dot com
2023-01-10 14:06 ` tromey at sourceware dot org
2023-01-11  4:32 ` euloanty at live dot com
2023-01-11  6:19 ` tromey at sourceware dot org
2023-01-11  6:47 ` euloanty at live dot com
2023-01-11  9:48 ` jwakely.gcc at gmail dot com
2023-01-11 15:13 ` tromey at sourceware dot org
2023-01-11 18:00 ` cvs-commit at gcc dot gnu.org
2023-01-11 18:02 ` tromey at sourceware dot org
2023-01-12 14:59 ` cvs-commit at gcc dot gnu.org
2023-01-12 14:59 ` tromey at sourceware dot org
2023-01-13  7:07 ` euloanty at live dot com
2023-01-13  7:07 ` euloanty at live dot com
2023-01-13 12:33 ` jwakely.gcc at gmail dot com
2023-01-13 19:12 ` tromey at sourceware dot org
2023-01-13 19:14 ` euloanty at live dot com
2023-01-13 21:27 ` tromey at sourceware dot org
2023-01-13 21:31 ` euloanty at live dot com
2023-01-14  6:29 ` brobecker at gnat dot com
2023-01-14  6:36 ` brobecker at gnat dot com
2023-01-14 17:11 ` tromey at sourceware dot org
2023-01-14 17:45 ` jwakely.gcc at gmail dot com
2023-01-14 17:52 ` jwakely.gcc at gmail dot com
2023-01-14 17:58 ` jwakely.gcc at gmail dot com
2023-01-18 16:55 ` tromey at sourceware dot org
2023-01-19  1:28 ` euloanty at live dot com
2023-01-19 16:49 ` tromey at sourceware dot org
2023-01-23 10:25 ` jwakely.gcc at gmail dot com
2023-01-23 10:54 ` jwakely.gcc at gmail dot com
2023-01-27 19:32 ` tromey at sourceware dot org
2023-01-28  2:27 ` euloanty at live dot com
2023-01-28  2:28 ` euloanty at live dot com
2023-01-28  2:30 ` euloanty at live dot com
2023-01-28  4:00 ` euloanty at live dot com
2023-01-28 10:08 ` jwakely.gcc at gmail dot com
2023-01-28 11:48 ` mark at klomp dot org
2023-01-29  3:41 ` tromey at sourceware dot org
2023-01-29  3:43 ` euloanty at live dot com
2023-01-29  3:44 ` euloanty at live dot com
2023-01-29  3:45 ` euloanty at live dot com
2023-01-29  3:54 ` euloanty at live dot com
2023-01-29 11:44 ` brobecker at gnat dot com
2023-01-29 13:27 ` mark at klomp dot org
2023-01-30  1:21 ` tromey at sourceware dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-29966-4717-ZcLgfvZd4l@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).