Mail Archives: cygwin/2006/02/25/10:01:58
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/
- Raw text -