X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Steven Brown Subject: Re: Fixing the state of C++ in Cygwin Date: Sat, 22 Apr 2006 19:20:53 -0700 Lines: 26 Message-ID: <444AE485.20000@ucsd.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: gerrit AT familiehaase DOT de, ptsekov AT gmx DOT net User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) In-Reply-To: X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 Steven Brown wrote: So, time for phase 2: > C++ programs are also affected by gcc bug #24196[1] (passing > std::string between exes and dlls), which causes hard to track down > crashes. This was discussed in an earlier thread[2] and the conclusion seemed to be that building with --enable-fully-dynamic-string[3] works around[4] this bug, and that gcc would be rebuilt[5] with it. I've built it as such as well and verified that it does seem to fix the bug, and have also made some m4 for autoconf[6] to detect if the bug exists at configure time. The discussion on 10/2005 seems to have stalled without a new gcc built with --enable-fully-dynamic-string being distributed. Can gcc get rebuilt with this option? [1] http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24196 [2] http://thread.gmane.org/gmane.os.cygwin/69962/focus=69962 [3] http://gcc.gnu.org/onlinedocs/libstdc++/configopts.html [4] http://article.gmane.org/gmane.os.cygwin/69989 [5] http://article.gmane.org/gmane.os.cygwin/69996 [6] https://svn.variadic.org/public/trunk/ax_dll_string_fix/ax_dll_string.m4 -- 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/