X-Spam-Check-By: sourceware.org Date: Wed, 12 Apr 2006 00:53:00 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Fixing the state of C++ in Cygwin Message-ID: <20060412045300.GB7046@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 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 On Tue, Apr 11, 2006 at 09:13:14PM -0700, Steven Brown wrote: >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? How about figuring out what the "for some reason" is that makes sed 4.1.5 (theoretically) fail? cgf -- 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/