public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/29110] Build failure for x86_64-w64-mingw32 GCC 13 host (because of win32 thread model?)
Date: Tue, 10 May 2022 14:17:53 +0000	[thread overview]
Message-ID: <bug-29110-4717-issg8xIIsk@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29110-4717@http.sourceware.org/bugzilla/>

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

--- Comment #7 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=20c4eb4226997c0de0a47d5d4c6c2eed21ed9af4

commit 20c4eb4226997c0de0a47d5d4c6c2eed21ed9af4
Author: Tom Tromey <tromey@adacore.com>
Date:   Mon May 9 11:48:40 2022 -0600

    Fix --disable-threading build

    PR build/29110 points out that GDB fails to build on mingw when the
    "win32" thread model is in use.  It turns out that the Fedora cross
    tools using the "posix" thread model, which somehow manages to support
    std::future, whereas the win32 model does not.

    While looking into this, I found that the configuring with
    --disable-threading will also cause a build failure.

    This patch fixes this build by introducing a compatibility wrapper for
    std::future.

    I am not able to test the win32 thread model build, but I'm going to
    ask the reporter to try this patch.

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

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

  parent reply	other threads:[~2022-05-10 14:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-01 16:25 [Bug build/29110] New: " euloanty at live dot com
2022-05-01 16:25 ` [Bug build/29110] " euloanty at live dot com
2022-05-06 16:43 ` tromey at sourceware dot org
2022-05-07 15:05 ` tromey at sourceware dot org
2022-05-07 20:24 ` euloanty at live dot com
2022-05-07 20:25 ` euloanty at live dot com
2022-05-09 17:16 ` tromey at sourceware dot org
2022-05-09 18:08 ` tromey at sourceware dot org
2022-05-09 23:47 ` euloanty at live dot com
2022-05-10 14:17 ` cvs-commit at gcc dot gnu.org [this message]
2022-05-10 14:19 ` 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-29110-4717-issg8xIIsk@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).