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: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Thu, 1 May 2003 10:56:58 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Chris Jefferson cc: cygwin AT cygwin DOT com Subject: Re: g++ newer version In-Reply-To: Message-ID: Importance: Normal MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 1 May 2003, Chris Jefferson wrote: > Hello! > > I'm really sorry because I suspect this is a FAQ.. > > I have a c program which shows up a bug in the current cygwin gcc and g++ > compilers > > ( http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8639 if > anyone is interested). It is fixed in 3.2.2 and above > > How long is it likely to be before 3.2.2 or 3.2.3 get merged into cygwin? Is > it a difficult task or just a case of only doing it when it seems worth it? > > Chris I suspect the latter. You can help out by taking the set of patches to the current Cygwin gcc package and tweaking them to apply to gcc 3.2.3 (and then sharing the result with this list). IIRC, gcc 3.2.3 compiles OOTB, but some Cygwin-specific additions are needed before it can become a package. Also, the current gcc maintainer (CGF) was seeking someone to take over maintainership of the gcc packages, so that would be even more helpful. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Knowledge is an unending adventure at the edge of uncertainty. -- Leto II -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/