public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "brechtsanders at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/99913] New: GCC11 fails to build for MinGW-w64 for Windows 32-bit
Date: Mon, 05 Apr 2021 08:11:40 +0000	[thread overview]
Message-ID: <bug-99913-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 99913
           Summary: GCC11 fails to build for MinGW-w64 for Windows 32-bit
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: brechtsanders at users dot sourceforge.net
  Target Milestone: ---

Created attachment 50509
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50509&action=edit
i686-w64-mingw32/libgomp/config.log

When building GCC 11 (including latest snapshot 20210404) against MinGW-w64 for
Windows 32-bit using an existing MinGW-w64 Windows 32-bit gcc configure stops
with the following error:

configure: error: unsupported system, cannot find sizeof (omp_lock_t)

This error is logged to file i686-w64-mingw32/libgomp/config.log which I have
attached.

At first glance it seems like it's not finding symbols that require
-lwinpthread

Note that there are no issues building GCC 11 against MinGW-w64 for Windows
64-bit.

             reply	other threads:[~2021-04-05  8:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-05  8:11 brechtsanders at users dot sourceforge.net [this message]
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
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@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).