X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Message-ID:	<b609cb3b0808221100v329c65b9ldc0f0c716978a405@mail.gmail.com>
Date:	Fri, 22 Aug 2008 14:00:58 -0400
From:	NightStrike <nightstrike AT gmail DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Compiling gcc for cygwin
MIME-Version:	1.0
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

I figured I would take the liberty of informing anyone from the cygwin
community that might not be on the gcc mailing lists.  After a recent
merge of the "tuples" branch of gcc to the mainline gcc, gcc stopped
being compilable by the 3.4.4 compiler that comes with cygwin.  There
are two bugs for this:

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37086
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37091

They have both been closed as invalid.

If cygwin ever wants to be able to support newer gcc compilers,
something needs to be done in this area.  There are several options,
and I am not advocating one over another.  I am instead just making
sure that the cygwin community is informed of the current state of gcc
4.4.

--
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/

- Raw text -