From: Earnie Boyd <earnie@users.sourceforge.net>
To: cygwin@cygwin.com
Cc: Keith Marshall <keithmarshall@users.sourceforge.net>
Subject: Re: mingw32-gcc and posix paths
Date: Thu, 30 Aug 2012 19:22:00 -0000 [thread overview]
Message-ID: <CA+sc5m=3=yDcWhRoqpcLU-fLEFKy9tPKubbAQkNgs9pmQTQ1ZQ@mail.gmail.com> (raw)
In-Reply-To: <k1ne6p$6im$1@ger.gmane.org>
On Thu, Aug 30, 2012 at 6:10 AM, Sven Köhler wrote:
> Am 29.08.2012 18:08, schrieb thoni56:
>> "i686-w64-mingw32-gcc" (which it is in my cygwin) works perfectly. Thanks!
>
> That is actually not MinGW (formely known as mingw32),
It is no such thing. It is known as MinGW.org.
> but MinGW-w64 (a
> new project, independent from the "old" MinGW32 project).
> That's why JonY pointed you at i686-pc-mingw32-gcc, which is the old
> MinGW (but not MinGW-w64) compiler.
>
> http://www.mingw.org/
> http://mingw-w64.sourceforge.net/
>
> If you have a choice, I'd recommend MinGW-w64 since the project is very
> alive and JonY provides regular updates of the cygwin packages.
We are as much alive as this adjunct mingw-w64 project is.
Sorry list, I could not let this slide by unchallenged.
--
Earnie
-- https://sites.google.com/site/earnieboyd
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2012-08-30 11:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 7:40 thoni56
2012-08-29 7:43 ` thoni56
2012-08-29 15:04 ` JonY
2012-08-29 18:02 ` thoni56
2012-08-30 16:45 ` Sven Köhler
2012-08-30 19:22 ` Earnie Boyd [this message]
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='CA+sc5m=3=yDcWhRoqpcLU-fLEFKy9tPKubbAQkNgs9pmQTQ1ZQ@mail.gmail.com' \
--to=earnie@users.sourceforge.net \
--cc=cygwin@cygwin.com \
--cc=keithmarshall@users.sourceforge.net \
/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).