Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3C3C9D05.D603F7F5@yahoo.com> Date: Wed, 09 Jan 2002 14:41:57 -0500 From: Earnie Boyd Reply-To: CU List X-Mailer: Mozilla 4.77 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: CU List Subject: Re: Compiling apps to Mingw32 with cygwin References: <3C3C999C DOT E7DBD5CC AT yahoo DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > Subject: Re: Compiling apps to Mingw32 with cygwin > Date: Wed, 9 Jan 2002 18:11:16 +0100 > From: "J. Henning Schwentner" > To: cygwin AT cygwin DOT com > > Am Montag, 7. Januar 2002 17:49 schrieben Sie: > > Jon Leichter wrote: > > > - Using CC="gcc -mno-cygwin" is good for compiling, but it's bad for GNU > > > Libtool, as I have mentioned. I use a wrapper script: CC=mgcc. What do > > > you think of this Earnie? > > > > Your wrapper script is a good idea but has the wrong name as has been > > pointed out already. It needs to be named i386-pc-mingw32-gcc and a > > copy as mingw32-gcc so that when specifying the --host=mingw32 or > > --host=i386-pc-mingw32 the configure script will find it appropriately. > > Of course to do this you also need to do the same for the binutils > > binaries. > > Do the binutils also support the -mno-cygwin switch? I'll leave that as an exercise for you to figure out. > Or can the > 386-pc-mingw32- files be simple links to the cygwin versions? > Yes, simply symlink will do. Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com -- 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/