Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Wed, 12 Mar 2003 10:54:13 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: cygwin gcc 3.4 and cygwin Message-ID: <20030312155413.GB14973@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <200303121439.h2CEdTUH348346@pimout4-ext.prodigy.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.1i On Wed, Mar 12, 2003 at 04:33:04PM +0100, Ronald Landheer-Cieslak wrote: >On Wed, 12 Mar 2003, Tim Prince wrote: >> On Wednesday 12 March 2003 03:20, Ronald Landheer-Cieslak wrote: >> > 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. >> It works fine OOTB, but it doesn't support the additional cygwin >> facilities. >I guess our definition of "works" is slightly different, then, but you're >right, gcc OOTB is a functional compiler on Cygwin :) FWIW, I build cygwin itself with an unpatched version of gcc several times a day. cgf -- 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/