X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: References: <30467239 DOT post AT talk DOT nabble DOT com> From: =?ISO-8859-1?Q?Fr=E9d=E9ric_Bron?= Date: Thu, 23 Dec 2010 08:08:43 +0100 Message-ID: Subject: Re: mingw-targeted cross-compiler question To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com > Basically, "stuff from mingw-w64.sf.net" > > The middle piece of the triplet is the vendor tag. =A0We at mingw-w64 > are the vendors. =A0We support win32 and win64, for both host and > target. =A0I admit it's confusing, but we didn't come up with a better > name fast enough. That is really good news. I am following the gcc announcements and was expecting a -w32... I can now try to replace -mno-cygwin by i686-w64-mingw32. Many thanks, Fr=E9d=E9ric -- 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