public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lh_mouse at 126 dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/99913] GCC11 fails to build for MinGW-w64 for Windows 32-bit
Date: Tue, 16 Jan 2024 05:17:57 +0000 [thread overview]
Message-ID: <bug-99913-4-y1rBtHzaAC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99913-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99913
LIU Hao <lh_mouse at 126 dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lh_mouse at 126 dot com
--- Comment #4 from LIU Hao <lh_mouse at 126 dot com> ---
Is there still such an error for you?
It looks to me that this linker command line did not contain `-pthread` unlike
the ones above. Maybe the configure script is worth looking at.
```
configure:16911: /R/winlibs32_stage/gcc-11-20210404/build_mingw/./gcc/xgcc
-B/R/winlibs32_stage/gcc-11-20210404/build_mingw/./gcc/
-L/R/winlibs32_stage/inst_gcc-11-20210404/share/gcc/i686-w64-mingw32/lib
-L/R/winlibs32_stage/inst_gcc-11-20210404/share/gcc/mingw/lib -isystem
/R/winlibs32_stage/inst_gcc-11-20210404/share/gcc/i686-w64-mingw32/include
-isystem /R/winlibs32_stage/inst_gcc-11-20210404/share/gcc/mingw/include
-B/R/winlibs32_stage/inst_gcc-11-20210404/share/gcc/i686-w64-mingw32/bin/
-B/R/winlibs32_stage/inst_gcc-11-20210404/share/gcc/i686-w64-mingw32/lib/
-isystem
/R/winlibs32_stage/inst_gcc-11-20210404/share/gcc/i686-w64-mingw32/include
-isystem
/R/winlibs32_stage/inst_gcc-11-20210404/share/gcc/i686-w64-mingw32/sys-include
--sysroot=/R/winlibs32_stage/gcc-11-20210404/build_mingw/mingw-w64 -o
conftest.exe -O0 -include confdefs.h -include
../../../libgomp/config/posix/omp-lock.h -s conftest.c -ldl >&5
D:\prog\winlibs32_stage\mingw32\i686-w64-mingw32\bin\ld.exe:
R:/winlibs32_stage/gcc-11-20210404/build_mingw/gcc/libgcc_eh.a(unwind-dw2.o):
in function `_gthread_once':
R:\winlibs32_stage\gcc-11-20210404\build_mingw\i686-w64-mingw32\libgcc/./gthr-default.h:700:
undefined reference to `pthread_once'
```
next prev parent reply other threads:[~2024-01-16 5:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 8:11 [Bug c/99913] New: " brechtsanders at users dot sourceforge.net
2021-04-05 8:23 ` [Bug target/99913] " pinskia at gcc dot gnu.org
2021-04-05 10:02 ` brechtsanders at users dot sourceforge.net
2021-04-05 10:05 ` brechtsanders at users dot sourceforge.net
2024-01-16 5:17 ` lh_mouse at 126 dot com [this message]
2024-01-19 7:00 ` brechtsanders at users dot sourceforge.net
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-99913-4-y1rBtHzaAC@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).