X-Spam-Check-By: sourceware.org
Date: Wed, 12 Apr 2006 12:31:21 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Fixing the state of C++ in Cygwin
Message-ID: <20060412103121.GA12493@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <e1huo3$i3v$1 AT sea DOT gmane DOT org> <20060412045300 DOT GB7046 AT trixie DOT casa DOT cgf DOT cx> <443C91B0 DOT 1020806 AT ucsd DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <443C91B0.1020806@ucsd.edu>
User-Agent: Mutt/1.4.2i
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

On Apr 11 22:35, Steven Brown wrote:
> 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.

 From the above thread you know what's the important difference between
Cygwin's sed 4.1.4 and 4.1.5.  There are three other major changes which
you will find in the NEWS file in the source code.  So the question is
this:

Is it a textmode/binmode issue and if so, why are the files created with
CRLF line endings at all?  If they are not created with CRLF line
endings on Linux, then there's no reason to create them with CRLF on
Cygwin.  As a first local solution, don't use textmode mounts.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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