X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Tue, 06 May 2008 21:55:27 -0400 From: Bob Rossi Subject: Re: Newbie needs help using mingw with cygwin In-reply-to: <48210A92.6A9674F6@dessent.net> To: cygwin AT cygwin DOT com Mail-followup-to: cygwin AT cygwin DOT com Message-id: <20080507015527.GC14306@brasko.net> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline References: <20080506231036 DOT GA27910 AT ednor DOT casa DOT cgf DOT cx> <20080506235700 DOT GA28066 AT ednor DOT casa DOT cgf DOT cx> <48210A92 DOT 6A9674F6 AT dessent DOT net> User-Agent: Mutt/1.5.17+20080114 (2008-01-14) 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 On Tue, May 06, 2008 at 06:49:06PM -0700, Brian Dessent wrote: > If you really want to use Cygwin as a host to build MinGW (native > windows) programs you need to treat it like cross compiling and specify > "--host=i686-pc-mingw32". But this is most likely NOT what you intended > to accomplish at all in this case. Hi Brian, I've been wondering about this. Why is it necessary to "cross-compile" from cygwin to mingw when the cygwin environment has the native mingw compiler? To me, it seems like if the mingw compiler is capable of running in the build environment, it should just be called and work. Is the cygwin mingw compiler a cross compiler? or is it the actual native mingw compiler? Thanks, Bob Rossi -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/