public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/106170] [13 Regression] x86_64-w64-mingw32 host GCC with win32 thread model does not provide pthread.h. lto-plugin fails with canadian compilation
Date: Wed, 27 Jul 2022 22:54:44 +0000	[thread overview]
Message-ID: <bug-106170-4-U04V1Kzzn3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106170-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106170

--- Comment #16 from cqwrteur <unlvsur at live dot com> ---
(In reply to Martin Liška from comment #15)
> Feel free to provide Windows implementation of the critical section.

make[4]: Leaving directory
'/home/cqwrteur/toolchains_build/gcc_build/x86_64-w64-mingw32/loongarch64-linux-gnu/gcc/gmp/doc'
/home/cqwrteur/toolchains/native/x86_64-w64-mingw32/lib/gcc/x86_64-w64-mingw32/13.0.0/../../../../x86_64-w64-mingw32/bin/ld:
cannot find -lpthread: No such file or directory
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:472: liblto_plugin.la] Error 1
make[3]: Leaving directory
'/home/cqwrteur/toolchains_build/gcc_build/x86_64-w64-mingw32/loongarch64-linux-gnu/gcc/lto-plugin'
make[2]: *** [Makefile:383: all] Error 2
make[2]: Leaving directory
'/home/cqwrteur/toolchains_build/gcc_build/x86_64-w64-mingw32/loongarch64-linux-gnu/gcc/lto-plugin'
make[1]: *** [Makefile:12790: all-lto-plugin] Error 2
make[1]: *** Waiting for unfinished jobs....

It still has not yet fixed

  parent reply	other threads:[~2022-07-27 22:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-03  4:50 [Bug lto/106170] New: win32 thread model does not " unlvsur at live dot com
2022-07-03  4:54 ` [Bug lto/106170] x86_64-w64-mingw32 host GCC with win32 thread model does not provide " unlvsur at live dot com
2022-07-03  5:30 ` unlvsur at live dot com
2022-07-03  5:42 ` unlvsur at live dot com
2022-07-03  6:16 ` unlvsur at live dot com
2022-07-03  7:00 ` unlvsur at live dot com
2022-07-04  6:41 ` [Bug lto/106170] [13 Regression] " rguenth at gcc dot gnu.org
2022-07-04  9:42 ` unlvsur at live dot com
2022-07-04 11:38 ` marxin at gcc dot gnu.org
2022-07-07 10:17 ` marxin at gcc dot gnu.org
2022-07-07 13:19 ` cvs-commit at gcc dot gnu.org
2022-07-07 13:20 ` marxin at gcc dot gnu.org
2022-07-07 15:33 ` unlvsur at live dot com
2022-07-08  7:59 ` marxin at gcc dot gnu.org
2022-07-08 20:08 ` pinskia at gcc dot gnu.org
2022-07-08 20:09 ` unlvsur at live dot com
2022-07-11  9:16 ` marxin at gcc dot gnu.org
2022-07-27 22:54 ` unlvsur at live dot com [this message]
2022-07-27 22:58 ` unlvsur at live dot com
2022-08-01  8:33 ` cvs-commit at gcc dot gnu.org
2022-08-01  8:33 ` marxin at gcc dot gnu.org
2023-02-02 16:19 ` jakub at gcc dot gnu.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-106170-4-U04V1Kzzn3@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).