X-Spam-Check-By:	sourceware.org
To:	cygwin AT cygwin DOT com
From:	Steven Brown <swbrown AT ucsd DOT edu>
Subject:	Fixing the state of C++ in Cygwin
Date:	Tue, 11 Apr 2006 21:13:14 -0700
Lines:	19
Message-ID:	<e1huo3$i3v$1@sea.gmane.org>
Mime-Version:	1.0
User-Agent:	Thunderbird 1.5 (Windows/20051201)
X-IsSubscribed:	yes
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

Currently in Cygwin, C++ apps using libtool will fail to build for some 
reason due to sed 4.1.5 - you have to downgrade to 4.1.4, which is not 
the default being installed.  C++ programs are also affected by gcc bug 
#24196[1] (passing std::string between exes and dlls), which causes hard 
to track down crashes.

I'd like to help get these fixed in Cygwin, but I'm not sure how to help 
out.  It seems the tasks to be done are:

1) Set sed 4.1.4 as the default until the reason 4.1.5 causes libtool 
failures is fixed.

2) Integrate the patch in gcc bug #24196 to Cygwin's build of gcc.

Could you point me in the right direction as to who to contact to help 
get these taken care of?


[1] http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24196


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