DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=C64BkC44fujf742d
	SaRgYzr3PiQ8/sv70/40g5F9ynAEb6WbozRC9rGyuMJfVIE2xKd/kqzshvnraq24
	qniQuDOTuPqnkmTwdtLR8YyXj6aRJNJEpP8pxbwLCbIlEnvtVgPW92uIr79J0Lk1
	vIc8fZwZ4KQ5lZtXpby8QfJfLEI=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: CR-LF handling behavior of SED changed recently - this breaks a lot of MinGW cross build scripts
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
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>
From: cyg Simple <cygsimple@gmail.com>
Message-ID: <15cab320-8b73-2553-b29d-6dfbea526854@gmail.com>
Date: Sat, 10 Jun 2017 09:42:59 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <0F7D3B1B3C4B894D824F5B822E3E5A175B270518@IRSMSX102.ger.corp.intel.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit


On 6/9/2017 11:01 AM, Soegtrop, Michael wrote:
> Dear cyg Simple,
> 
>> but it would be most beneficial if you caused the stdio of your
>> Windows applications to be in binary format instead of text format.  Then the
>> CR wouldn't be an issue during the pipe process.  Why does your applications
>> stdio need to be in text format instead of binary format?
> 
> it is not my application I have issues with. I am building many open source tools and libraries which are maintained by others, and as you said, these others have every right to deny implementing windows specific workarounds in their tools or build scripts. Why should anybody use "wb" mode to open a file in a Linux centric app or mess around with the input of sed to remove CRs in a build script for such an app? Of cause the same is true for cygwin, except that I think building MinGW apps is an intended use case for cygwin. But then it needs to have ways to deal with MinGW programs which behave like MinGW programs should, and this means ending lines with cr-lf. 

I see the conversation gets a bit lengthy already and many opinions
exist.  I didn't say to use 'wb' with every open.  I said set the stdio,
(i.e. STDIN, STDOUT, STDERR) to binary mode.  See the documentation for
the MinGW lib/binmode.o object use when linking the binary.

As for Cygwin being an intended use case for building MinGW apps, why do
you think it was forked as MSYS?  Cygwin itself has never completely
dealt easily with cross compatibility between Windows and Cygwin itself.
 If you wish to use Cygwin as is for your work with building MinGW tools
then you'll need to set your standards to work within that environment.

In other follow-up email you explain your use case, I suggest that MSYS
is the better fit for you with that use case.  Check into it.

-- 
cyg Simple

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