MIME-Version: 1.0
In-Reply-To: <k1ne6p$6im$1@ger.gmane.org>
References: <1346220462071-92376.post@n5.nabble.com>	<1346220956451-92378.post@n5.nabble.com>	<503DC812.5060704@users.sourceforge.net>	<1346256499860-92389.post@n5.nabble.com>	<k1ne6p$6im$1@ger.gmane.org>
Date: Thu, 30 Aug 2012 07:24:54 -0400
Message-ID: <CA+sc5m=3=yDcWhRoqpcLU-fLEFKy9tPKubbAQkNgs9pmQTQ1ZQ@mail.gmail.com>
Subject: Re: mingw32-gcc and posix paths
From: Earnie Boyd <earnie@users.sourceforge.net>
To: cygwin@cygwin.com
Cc: Keith Marshall <keithmarshall@users.sourceforge.net>
Content-Type: text/plain; charset=UTF-8
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Content-Transfer-Encoding: 8bit

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