X-Spam-Check-By: sourceware.org Message-ID: <463DDE7F.5010105@cwilson.fastmail.fm> Date: Sun, 06 May 2007 09:56:15 -0400 From: Charles Wilson User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Dave Korn CC: cygwin AT cygwin DOT com Subject: Re: Successful build of GCC 4.2.0 RC3 on latest Cygwin snapshot 20070427 References: <2b2c01c78fa5$d94a27c0$0200a8c0 AT AMD2500> <01f001c78fc6$c916ce00$2e08a8c0 AT CAM DOT ARTIMI DOT COM> In-Reply-To: <01f001c78fc6$c916ce00$2e08a8c0@CAM.ARTIMI.COM> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 [removed mailing lists other than cygwin] Dave Korn wrote: > I'm doing that. Should be finished in another day or so... :-O 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. -- Chuck -- 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/