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 Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Authentication-Warning: localhost.localdomain: ronald owned process doing -bs Date: Wed, 12 Mar 2003 12:20:58 +0100 (CET) From: Ronald Landheer-Cieslak X-X-Sender: ronald AT localhost DOT localdomain To: Eugene Rosenzweig cc: cygwin AT cygwin DOT com Subject: Re: cygwin gcc 3.4 and cygwin In-Reply-To: <004801c2e87b$e7bba110$a400a8c0@bluebox> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII The cygwin target is i686-pc-cygwin That, and Cygwin without gcc would be pretty useless, so I don't worry too much :) rlc BTW: the FSF-provided gcc doesn't work OOTB on Cygwin, IIRC: there are a couple of patches to apply and a bit of development to be done each time. You might say that there is no "official" gcc on Cygwin as is :) On Wed, 12 Mar 2003, Eugene Rosenzweig wrote: > The latest message in gcc-announce > http://gcc.gnu.org/ml/gcc-announce/2003/msg00001.html says that i?86-*-win32 > target will be deprecated as from gcc 3.4 (no date set). The only win32 > target on the list of supported platforms > http://gcc.gnu.org/install/specific.html is the cygwin one. Will there be no > more official cygwin gcc port as of 3.4? > > > > -- > 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/ > > -- 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/