X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Wlodek Szafran <wlodek DOT szafran AT hwcn DOT org>
Subject:  Re: sed: 4.1.5 breaks libtool generation
Date: Sat, 25 Feb 2006 04:19:46 +0000 (UTC)
Lines: 24
Message-ID:  <loom.20060225T045242-102@post.gmane.org>
References:  <43FE1CEF DOT 9030905 AT users DOT sourceforge DOT net> <43FECB5A DOT 7060908 AT cwilson DOT fastmail DOT fm> <20060224094106 DOT GK4294 AT calimero DOT vinschen DOT de> <dtmpf1$o83$1 AT sea DOT gmane DOT org> <20060224114151 DOT GL4294 AT calimero DOT vinschen DOT de>
Mime-Version:  1.0
Content-Type:  text/plain; charset=us-ascii
Content-Transfer-Encoding:  7bit
User-Agent: Loom/3.14 (http://gmane.org/)
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

Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:

> sed's internal getline enforces CRLF line ending recognition regardless
> of the mount type, which results in mishandling of binary input files.
> sed has no -b/--binary option.  So by using newlib's getline which
> doesn't enforce CRLF->LF conversion, sed 4.1.5 should be actually
> "fixed", FWIW.  If you need CRLF->LF conversion, you can use a filter
> application like dos2unix.
> 
> Nothing's impossible, but I'd be actually surprised if that's the cause
> for the libtool misbehaviour.

It seems to be the true reason, though.  I've noticed this strange behaviour
with one of configure scripts I'm using.  The script uses sed to edit a file
which consists of description/value pairs and before version 4.1.5 there were no
problems.  After updating sed to this version, I've noted that the contents of
the mentioned file were left unedited after the script ran, which was puzzling
until reading here about the line endings.  A simple experiment shows that if
the input file has CRLF line endings, no replacements of text happen -- the
output file seems to be just a copy of the input one.  However, after the input
file was converted to LF line endings, everything went back to normal.

Best regards.



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