From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: problem using gcc-core for compile qemu
Date: Fri, 8 Jan 2021 07:55:44 +0100 [thread overview]
Message-ID: <4e7d50f5-e1bd-0232-93b4-0d6d03340775@gmail.com> (raw)
In-Reply-To: <ea1fab30-88b1-3096-8080-9876cef32116@gmail.com>
On 08.01.2021 06:52, Marco Atzeri wrote:
> On 07.01.2021 23:33, juan carlos rebate rodriguez via Cygwin wrote:
>> El jue, 07-01-2021 a las 15:39 +0100, Marco Atzeri via Cygwin escribió:
> To compile for Windows on Cygwin you need to use a cross-compiler.
> The 64 bit one is in:
ehm, copy and paste error.
This is the 32bit one
> $ cygcheck -l mingw64-i686-gcc-core | grep usr/bin
> /usr/bin/i686-w64-mingw32-cpp.exe
> /usr/bin/i686-w64-mingw32-gcc.exe
> /usr/bin/i686-w64-mingw32-gcc-10.exe
> /usr/bin/i686-w64-mingw32-gcc-ar.exe
> /usr/bin/i686-w64-mingw32-gcc-nm.exe
> /usr/bin/i686-w64-mingw32-gcc-ranlib.exe
> /usr/bin/i686-w64-mingw32-gcov.exe
> /usr/bin/i686-w64-mingw32-gcov-dump.exe
> /usr/bin/i686-w64-mingw32-gcov-tool.exe
> /usr/bin/i686-w64-mingw32-lto-dump.exe
and this the 64bit one
$ cygcheck -l mingw64-x86_64-gcc-core |grep usr/bin
/usr/bin/x86_64-w64-mingw32-cpp.exe
/usr/bin/x86_64-w64-mingw32-gcc.exe
/usr/bin/x86_64-w64-mingw32-gcc-10.exe
/usr/bin/x86_64-w64-mingw32-gcc-ar.exe
/usr/bin/x86_64-w64-mingw32-gcc-nm.exe
/usr/bin/x86_64-w64-mingw32-gcc-ranlib.exe
/usr/bin/x86_64-w64-mingw32-gcov.exe
/usr/bin/x86_64-w64-mingw32-gcov-dump.exe
/usr/bin/x86_64-w64-mingw32-gcov-tool.exe
/usr/bin/x86_64-w64-mingw32-lto-dump.exe
next prev parent reply other threads:[~2021-01-08 6:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 3:23 Juan carlos Rebate
2021-01-07 3:37 ` Eliot Moss
2021-01-07 13:43 ` Eliot Moss
2021-01-07 14:39 ` Marco Atzeri
2021-01-07 14:53 ` Csaba Raduly
2021-01-07 16:18 ` Marco Atzeri
2021-01-07 17:00 ` Eliot Moss
2021-01-07 22:33 ` juan carlos rebate rodriguez
2021-01-08 5:52 ` Marco Atzeri
2021-01-08 6:55 ` Marco Atzeri [this message]
2021-01-08 8:42 ` Arthur Norman
2021-01-08 13:06 ` Eliot Moss
2021-01-08 13:19 ` Marco Atzeri
2021-01-08 20:54 ` juan carlos rebate rodriguez
2021-01-08 22:32 ` Lee
2021-01-08 22:33 ` Brian Inglis
2021-01-07 17:21 ` Brian Inglis
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=4e7d50f5-e1bd-0232-93b4-0d6d03340775@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
/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).