public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "euloanty at live dot com" <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: Sat, 07 May 2022 20:24:36 +0000	[thread overview]
Message-ID: <bug-29110-4717-JMrjGfQeKa@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 #2 from cqwrteur <euloanty at live dot com> ---
(In reply to Tom Tromey from comment #1)
> What version of gcc are you using?
> 
> When I do a build using the Fedora mingw cross toolchain, it works fine,
> and AFAIK this gcc also doesn't support win32 threads.
> My version is:
> 
> murgatroyd. x86_64-w64-mingw32-gcc --version
> x86_64-w64-mingw32-gcc (GCC) 10.3.1 20210422 (Fedora MinGW 10.3.1-2.fc34)

GCC 13. You are probably using POSIX thread model. I am using win32 thread
model that does not provide C++ thread or even mutex facility at all for
libstdc++

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

  parent reply	other threads:[~2022-05-07 20:24 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 [this message]
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
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-JMrjGfQeKa@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).