Message-Id: <200201071944.g07Jimr16287@delorie.com> 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 Content-Type: text/plain; charset="iso-8859-1" From: "J. Henning Schwentner" To: Subject: Re: Compiling apps to Mingw32 with cygwin Date: Mon, 7 Jan 2002 20:45:18 +0100 X-Mailer: KMail [version 1.3.2] References: <3C39D182 DOT 5B9E8EC AT yahoo DOT com> In-Reply-To: <3C39D182.5B9E8EC@yahoo.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Dear Earnie, I do not get it with the --build switch. Am I not building on i686-pc-cygwin? Is it i368-pc-mingw because I use the mingw-headers? But I use the cygwin-compiler. Sorry, but I am confused a bit ... > 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. Should'nt these scripts be included in the standard cygwin-gcc- (and binutils-) distribution? It would be very easy to include them, and compiling for the mingw32 target would also be a lot easier. -- J. Henning Schwentner Lanthan Software KG _________________________________________________________ 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/