X-Spam-Check-By:	sourceware.org
Date:	Tue, 2 May 2006 16:06:09 +0200 (MET DST)
From:	Angelo Graziosi <Angelo DOT Graziosi AT roma1 DOT infn DOT it>
To:	swbrown AT ucsd DOT edu
cc:	cygwin AT cygwin DOT com
Subject:	Re: Fixing the state of C++ in Cygwin
Message-ID:	<Pine.OSF.4.21.0605021559490.11646-100000@ax0rm1.roma1.infn.it>
MIME-Version:	1.0
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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

Steven Brown  wrote:

> There's simply no way to solve this for all cases without a recompile of
> libstdc++. 


I wrote:

> Your test case DOES NOT abort if one builds it with GCC that was rebuilt
> whitout that patch but configured with --enable-fully-dynamic-string!


Your test case (http://svn.variadic.org/public/trunk/weirdbug/) DOES NOT
abort also if one rebuilds GCC WITHOUT ADDING
--enable-fully-dynamic-string BUT APPLYING the patch PR24196!



Cheers,

   Angelo.


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