Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <04fc01c19bc0$b5c97730$0200a8c0@lifelesswks> From: "Robert Collins" To: "Earnie Boyd" , "Jon Leichter" Cc: , References: <3C407AFB.DC2871B5@yahoo.com> Subject: Re: Compiling apps to Mingw32 with cygwin Date: Sun, 13 Jan 2002 10:27:31 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 12 Jan 2002 23:27:27.0313 (UTC) FILETIME=[B2751C10:01C19BC0] ----- Original Message ----- From: "Earnie Boyd" > 1) `gcc -mno-cygwin' is not a cross compile. > 2) it is possible to emulate a cross build system using a scripted `gcc > -mno-cygwin' and symlinks. > 3) `gcc -mno-cygwin' switches the build environment from Cygwin to > MinGW. Earnie, on 3) I believe we have a terminology problem. gcc -mno-cygwin changes the _build target_ to mingw32, no the build _environment_. In the context of configure scripts the build _environment_ is the platform hosting the running script, and doing the compilation - that is cygwin. > > You said this was wrong. To be consisent with future behavior, it seems that > > I must specify build. So if you're suggesting that I'm not cross-compiling, > > then it would be: > > > > $ env CC=mgcc ./configure --host=i686-pc-mingw32 --build=i686-pc-mingw32 > > > > This is what I would do. IMO this is wrong (wrong build value) - see my comment earlier. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/