DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=EWRlZlFUlTl17pajTX5MfCCGynQcV6La3cdqi3oLnwr
	KTEQkIiQZ02h9EbNOMKHmguARI1Qab5lb6MHcUieUsRsijyC4Wd04oTt5e9g1lP0
	mDpcfTsjL0Bz5LxnzPbmd2YOG8Z/+rqz0tyM43i0A8GQIPKU73AeXicAGJv0bUwg
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
In-Reply-To: <76b29936-06a3-bfd1-0d6c-02c95034f9d5@t-online.de>
References: <0F7D3B1B3C4B894D824F5B822E3E5A175B2636E4@IRSMSX103.ger.corp.intel.com> <a53282b6-d00c-aad8-76a6-26b4089a9623@redhat.com> <0F7D3B1B3C4B894D824F5B822E3E5A175B26CE47@IRSMSX102.ger.corp.intel.com> <59399CC5.60900@tlinx.org> <417f84ac-5d9f-dc50-e912-973e90b8a128@redhat.com> <0F7D3B1B3C4B894D824F5B822E3E5A175B26F278@IRSMSX102.ger.corp.intel.com> <34b26965-34c2-b5f0-a3f2-b2c3df344b08@gmail.com> <0F7D3B1B3C4B894D824F5B822E3E5A175B270518@IRSMSX102.ger.corp.intel.com> <5313de97-d9bd-d9c9-cb4a-254a3eadcf4a@redhat.com> <0F7D3B1B3C4B894D824F5B822E3E5A175B2705E9@IRSMSX102.ger.corp.intel.com> <76b29936-06a3-bfd1-0d6c-02c95034f9d5@t-online.de>
From: Erik Soderquist <ErikSoderquist@gmail.com>
Date: Fri, 9 Jun 2017 15:30:41 -0400
Message-ID: <CACoZoo1P+75e9PMRB=BZER9MDo-f=2QV_5absnthaAJu3US5FA@mail.gmail.com>
Subject: Re: CR-LF handling behavior of SED changed recently - this breaks a lot of MinGW cross build scripts
To: cygwin <cygwin@cygwin.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit

On Fri, Jun 9, 2017 at 2:42 PM, Hans-Bernhard Bröker wrote:
>> I don't see another way than having sed strip away the CRs. It
>> doesn't make sense to build programs intended to be run under plain
>> Windows such that they do not produce CRs.
>
>
> I believe it makes much more sense than you think.  Hardly any Windows tool
> worth using actually _needs_ those CRs in the first place.

I agree heartily with this; the only Windows tool I use that is
actually dependent on CR is notepad, and usually that is only for a
lazy verification that CR is/isn't present

Everything I've written for dealing with Windows CR infested outputs
in *nix environments I strip all CRs as my first step, and do not put
CRs in my output; so far no complaints from end users about the
missing CRs.

-- Erik

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple