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++/99401] New: GCC11 MinGW-w64 32-bit build fails with undefined reference to `LC0'
Date: Fri, 05 Mar 2021 08:53:54 +0000 [thread overview]
Message-ID: <bug-99401-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99401
Bug ID: 99401
Summary: GCC11 MinGW-w64 32-bit build fails with undefined
reference to `LC0'
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 50301
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50301&action=edit
make output
When building GCC11 (last tested with 11-20210228) for Windows 32-bit with
MinGW-w64 the build fails with undefined references to LC0/LC1/LC2/LC3.
My build was done using the following configure command:
../configure --prefix=/R/winlibs32_stage/inst_gcc-11-20210228/share/gcc
--build=i686-w64-mingw32 --host=i686-w64-mingw32 --with-pkgversion=MinGW-W64
i686-posix-dwarf, built by Brecht Sanders --with-tune=generic
--enable-checking=release --enable-threads=posix --with-dwarf2
--disable-sjlj-exceptions --disable-libunwind-exceptions
--disable-serial-configure --disable-bootstrap --enable-host-shared
--enable-plugin --disable-default-ssp --disable-rpath --disable-libstdcxx-pch
--enable-libstdcxx-time=yes --disable-libstdcxx-debug
--disable-version-specific-runtime-libs --with-stabs --disable-symvers
--enable-languages=c,c++,lto,objc,obj-c++,d --disable-gold --disable-nls
--disable-stage1-checking --disable-win32-registry --disable-multilib
--enable-ld --enable-libquadmath --enable-libada --enable-libssp
--enable-libstdcxx --enable-lto --enable-fully-dynamic-string --enable-libgomp
--enable-graphite --enable-mingw-wildcard
--with-mpc=/d/Prog/winlibs32_stage/custombuilt
--with-mpfr=/d/Prog/winlibs32_stage/custombuilt
--with-gmp=/d/Prog/winlibs32_stage/custombuilt
--with-isl=/d/Prog/winlibs32_stage/custombuilt --enable-install-libiberty
--enable-__cxa_atexit --without-included-gettext --with-diagnostics-color=auto
--with-libiconv --with-system-zlib
--with-build-sysroot=/R/winlibs32_stage/gcc-11-20210228/mingw-w64
--enable-large-address-aware
CFLAGS=-I/d/Prog/winlibs32_stage/custombuilt/include/libdl-win32
Note that I was able to build the 32-bit compiler once, but I had to disable
fortran to work around this error. This is the second iteration where I try to
build GCC 11-20210228 with the same version of GCC from the first iteration.
Windows 64-bit builds work fine, so this error is limited to Windows 32-bit.
Any idea what causes this?
next reply other threads:[~2021-03-05 8:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 8:53 brechtsanders at users dot sourceforge.net [this message]
2021-03-05 9:19 ` [Bug c++/99401] " ebotcazou at gcc dot gnu.org
2021-03-05 10:33 ` [Bug target/99401] " brechtsanders at users dot sourceforge.net
2021-03-05 11:23 ` ebotcazou at gcc dot gnu.org
2021-03-05 12:39 ` [Bug target/99401] Rebuilding the compiler with itself fails at -O2 ebotcazou at gcc dot gnu.org
2021-03-05 12:44 ` brechtsanders at users dot sourceforge.net
2021-03-05 12:51 ` jakub at gcc dot gnu.org
2021-04-29 13:49 ` jakub at gcc dot gnu.org
2021-04-29 17:21 ` 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-99401-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).