X-Spam-Check-By:	sourceware.org
Message-ID:	<443C91B0.1020806@ucsd.edu>
Date:	Tue, 11 Apr 2006 22:35:44 -0700
From:	Steven Brown <swbrown AT ucsd DOT edu>
User-Agent:	Thunderbird 1.5 (Windows/20051201)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Fixing the state of C++ in Cygwin
References:	<e1huo3$i3v$1 AT sea DOT gmane DOT org> <20060412045300 DOT GB7046 AT trixie DOT casa DOT cgf DOT cx>
In-Reply-To:	<20060412045300.GB7046@trixie.casa.cgf.cx>
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

Christopher Faylor wrote:

> How about figuring out what the "for some reason" is that makes sed 4.1.5
> (theoretically) fail?

The thread regarding sed 1.4.5 and libtool:
http://www.cygwin.com/ml/cygwin/2006-02/msg00846.html

Wouldn't it be best to first return to sed 4.1.4 before debugging why 
upgrading to sed 4.1.5 is problematic?  It's left Cygwin installs in a 
broken state for C++ compiles since February.

I can look into the problem with sed 4.1.5 as well, but I'd like to see 
Cygwin stay in a working state as much as possible.

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