public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/105352] Building cross-compiler for host i686-w64-mingw32, target mips32-elf, fails
Date: Fri, 22 Apr 2022 20:56:52 +0000 [thread overview]
Message-ID: <bug-105352-4-uLEDTvDDod@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105352-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105352
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|UNCONFIRMED |RESOLVED
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
>../gcc-11.3.0/configure --host=i686-w64-mingw32 --target=mips32-elf --disable-nls
>I want the compiled executable files to run natively on Windows 32-bits as .exe , hence the host `i686-w64-mingw32`.
You don't have a i686-w64-mingw32 cross compiler installed though.
So you are just doing something which won't work until you get a cross compiler
on the machine.
next prev parent reply other threads:[~2022-04-22 20:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 20:48 [Bug other/105352] New: " dragorn421 at gmail dot com
2022-04-22 20:56 ` pinskia at gcc dot gnu.org [this message]
2022-04-22 20:59 ` [Bug other/105352] " dragorn421 at gmail dot com
2022-04-22 22:55 ` dragorn421 at gmail 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-105352-4-uLEDTvDDod@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).