DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=Q3
	LepHWF05a5WOumx5VSNxSzrX0DUIAxB/pcoVdCtymi5jT3alh1lH+39IrHDkZjgw
	kFRk7OyZL/bt9PQ3Lim+cxWGikbQ73QsyHxFFeLo1APraD8wzAX0TSlGtIR8TP3a
	wePGDU68SO7XabeB1RQPNL1YV1r7a3FlycGMy3aqU=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
In-Reply-To: <56EB2575.5000209@cygwin.com>
References: <56EB2575.5000209@cygwin.com>
Date: Mon, 21 Mar 2016 15:12:39 -0400
Message-ID: <CAD8GWsuU5t2ftMf3Oe+DWE65rrgkquR96sMGONmykGicpx5Mjw@mail.gmail.com>
Subject: Re: Removed: mingw.org toolchain
From: Lee <ler762@gmail.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Content-Type: text/plain; charset=UTF-8

On 3/17/16, Yaakov Selkowitz wrote:
> The old mingw.org (i686-pc-mingw32) toolchain has been removed from the
> Cygwin distribution.  It was unmaintained (both upstream and downstream)
> and limited to 32-bit support.
>
> Users who wish to cross-compile for native Windows should use the
> mingw64-* ({i686,x86_64}-w64-mingw32) toolchains instead.

I'd like to cross-compile to native Windows 32 bit executables.  So
I'd install mingw64-i686-gcc-core even tho it says "GCC for Win64
toolchain" - correct?

And then ./configure  --host=i686-w64-mingw32
or use some other host value?


nit-picky, but should the FAQ be updated to remove "mingw-gcc"?

6.13 How do I compile a Win32 executable that doesn't use Cygwin?
The compilers provided by the mingw-gcc, mingw64-i686-gcc, and
mingw64-x86_64-gcc packages link against standard Microsoft DLLs
instead of Cygwin.

Thanks,
Lee

--
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