public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ctice at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/101711] Error when gcc cross compile libvtv
Date: Wed, 04 Aug 2021 16:09:25 +0000 [thread overview]
Message-ID: <bug-101711-4-N6HcmrJJfg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101711-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101711
ctice at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ctice at gcc dot gnu.org
--- Comment #4 from ctice at gcc dot gnu.org ---
Is there something special I need to download, set up, or build in order to do
mingw32 cross-compiles?
I'm getting configure/build failures even when I omit enabling vtable verify; I
also don't know where/how to get the mcf thread libraries?
[Instructions for both of these are necessary if I am to debug the libvtv
issue].
Just to see if this was related to libvtv or not, I tried:
$ ../configure --disable-multilib --disable-nls --enable-languag
es=c,c++,lto --enable-version-specific-runtime-libs
--enable-fully-dynamic-strin
g --enable-large-address-aware --enable-mingw-wildcard
--target=x86_64-w64-mingw
32 --with-local-prefix=/usr/local/x86_64-w64-mingw32
$ make
(Notice that I omitted the --enable-threads=mcf and the --enable-vtable-verify
flags).
I got:
...
make[2]: Leaving directory
'/usr/local/google3/cmtice/gcc-fsf.clean.novtv.obj/libcc1'
Checking multilib configuration for libgcc...
Configuring in x86_64-w64-mingw32/libgcc
configure: loading cache ./config.cache
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-w64-mingw32
checking for --enable-version-specific-runtime-libs... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking for gawk... gawk
checking for x86_64-w64-mingw32-ar... x86_64-w64-mingw32-ar
checking for x86_64-w64-mingw32-lipo... x86_64-w64-mingw32-lipo
checking for x86_64-w64-mingw32-nm...
/usr/local/google3/cmtice/gcc-fsf.clean.novtv.obj/./gcc/nm
checking for x86_64-w64-mingw32-ranlib... x86_64-w64-mingw32-ranlib
checking for x86_64-w64-mingw32-strip... x86_64-w64-mingw32-strip
checking whether ln -s works... yes
checking for x86_64-w64-mingw32-gcc...
/usr/local/google3/cmtice/gcc-fsf.clean.novtv.obj/./gcc/xgcc
-B/usr/local/google3/cmtice/gcc-fsf.clean.novtv.obj/./gcc/
-L/usr/local/x86_64-w64-mingw32/lib -L/usr/local/mingw/lib -isystem
/usr/local/x86_64-w64-mingw32/include -isystem /usr/local/mingw/include
-B/usr/local/x86_64-w64-mingw32/bin/ -B/usr/local/x86_64-w64-mingw32/lib/
-isystem /usr/local/x86_64-w64-mingw32/include -isystem
/usr/local/x86_64-w64-mingw32/sys-include
checking for suffix of object files... configure: error: in
`/usr/local/google3/cmtice/gcc-fsf.clean.novtv.obj/x86_64-w64-mingw32/libgcc':
configure: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details
make[1]: *** [Makefile:13771: configure-target-libgcc] Error 1
make[1]: Leaving directory '/usr/local/google3/cmtice/gcc-fsf.clean.novtv.obj'
make: *** [Makefile:968: all] Error 2
Please update this bug with further instructions. Thank you.
next prev parent reply other threads:[~2021-08-04 16:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-01 4:06 [Bug other/101711] New: " bootmgr at 163 dot com
2021-08-01 4:07 ` [Bug other/101711] " bootmgr at 163 dot com
2021-08-01 6:45 ` pinskia at gcc dot gnu.org
2021-08-02 21:07 ` egallager at gcc dot gnu.org
2021-08-04 16:09 ` ctice at gcc dot gnu.org [this message]
2021-08-05 23:20 ` bootmgr at 163 dot com
2021-08-06 1:02 ` ctice at gcc dot gnu.org
2021-08-06 1:05 ` ctice at gcc dot gnu.org
2021-08-06 3:30 ` bootmgr at 163 dot com
2021-08-27 8:58 ` pinskia at gcc dot gnu.org
2021-09-01 23:54 ` ctice at gcc dot gnu.org
2021-09-10 12:24 ` bootmgr at 163 dot com
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-101711-4-N6HcmrJJfg@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).