public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bootmgr at 163 dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/101711] Error when gcc cross compile libvtv
Date: Fri, 06 Aug 2021 03:30:06 +0000 [thread overview]
Message-ID: <bug-101711-4-Mcmd4C7LGF@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
--- Comment #8 from bootmgr at 163 dot com <bootmgr at 163 dot com> ---
(In reply to ctice from comment #6)
> I applied the patch supplied in comment 5. I added
> --with-sysroot=/usr/local to my configure command (still not using
> --enable-threads=mcf or --enable-vtable-verify). Now it configures, but the
> make command fails while building gcc, complaining that:
>
> The directory that should contain system headers does not exist:
> /usr/local/mingw/include
>
> Which is completely true. I'm working on an elf/linux machine (x86_64) and
> I have no mingw headers. Where can I get the appropriate headers (and
> anything else I will need) in order to make this cross compile work?
Compiling a cross toolchain can be a bit complicated.
The mingw-w64 wiki has documentation on how to compile the mingw cross
toolchain.
https://sourceforge.net/p/mingw-w64/wiki2/Cross%20Win32%20and%20Win64%20compiler/
If you want other thread models (other than win32), you can compile the
winpthreads library (--enable-threads=posix) or copy release/mingw64/*
(--enable-threads) from the mcfgthread repository to
/path/to/install/x86_64-w64-mingw32/ after compiling crt.
next prev parent reply other threads:[~2021-08-06 3:30 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
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 [this message]
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-Mcmd4C7LGF@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).