X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Message-ID: Date: Fri, 22 Aug 2008 14:00:58 -0400 From: NightStrike To: cygwin@cygwin.com Subject: Compiling gcc for cygwin MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: 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 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/