X-Spam-Check-By: sourceware.org
Message-ID: <001a01c78ff2$0db23970$0200a8c0@AMD2500>
From: "Aaron Gray" <angray AT beeb DOT net>
To: "Charles Wilson" <cygwin AT cwilson DOT fastmail DOT fm>
Cc: <cygwin AT cygwin DOT com>
References: <2b2c01c78fa5$d94a27c0$0200a8c0 AT AMD2500> <01f001c78fc6$c916ce00$2e08a8c0 AT CAM DOT ARTIMI DOT COM> <463DDE7F DOT 5010105 AT cwilson DOT fastmail DOT fm>
Subject: Re: Successful build of GCC 4.2.0 RC3 on latest Cygwin snapshot 20070427
Date: Sun, 6 May 2007 16:20:16 +0100
MIME-Version: 1.0
Content-Type: text/plain; 	format=flowed; 	charset="iso-8859-1"; 	reply-type=response
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook Express 6.00.2900.3028
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

> Danger, Will Robinson: the g++ from gcc-4.2.0 does not have any support 
> for catching exceptions thrown across DLL boundaries.  Nor does it include 
> the fix for empty strings (PR24196).
>
> The former problem can be solved by building libgcc shared, and 
> libstdc++/libsupc++ shared.  Absent modern libtool support (which is 
> partially present only in trunk), this will be tricky.  But even when you 
> get an initial DLL version of these libraries, there will certainly be a 
> long shakedown period...
>
> So don't anybody here on the cygwin list get too excited yet. <g>

Yes, it looks like we are getting a few instances of this on the LLVM test 
suite.

Oh well, looks like the Cygwin build is not going to make it for the LLVM 
2.0 Release.

Aaron


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