X-Recipient:	archive-cygwin AT delorie DOT com
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=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; 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; s=default; bh=7dhhSY33y2iWj1PoIp7Ux7
	f0VEM=; b=KkDBGblUk2FghU5zZkhC45xpIqePHuYy3Qz0buZJWGelBNSmRNLPYM
	jxEuov5q5L6h6A0H58XLPIrG8p2r03rEf3gkkA3r6zHzAMqjWG/0XLAifEUd+Dw+
	5ir5uInkq9Nf10sjFkc5dFXkPQIkLiBQJo0yo56xtFyNfhZa+W914=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-2.5 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=dear, Dear, wish, HContent-Transfer-Encoding:8bit
X-HELO:	mail-it0-f50.google.com
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=MPejF6xYM7dHVAPl7Jfj/5gJw1y9fE8CYQGOBQyenN0=; b=r27UUdCgllQsgzEmF8Mtk3K+Coip9LJKGUwvGltBsoE+q8h5i3qdFliJJW1YCvSiIb eZ9iQZusfom9zoHWCRwLt1RA9wfwtlmEgsKc8FcfNZ7zYi+EUWyTQOcXBdAM8+js+rxp muoDiU69I7h3tQHYfYdZqBFYINargJZ1nU9Fj2/XQItawulBkRKopldKUrkhm/bICTw7 a6a8SFvEX7PTmIHh3u1nGjavbx1fY613li5AAeFY+ccTwHofTswIN2LunZAy/n+cHKeL HVoKU1hTVDx/JBaDTfo1WB3guXqzE407/928M3PWuSJLXrSkPW8WCXiOg2lYf3QXGX+b 4whw==
X-Gm-Message-State:	AODbwcAtiv9A5Iz1mXzJquE4L4w3jWK3ubpQROUOtQ0W07jQBpC9QyHP 9zbMQX4zq/hn7H9q
X-Received:	by 10.36.147.69 with SMTP id y66mr4583998itd.61.1497102177601; Sat, 10 Jun 2017 06:42:57 -0700 (PDT)
Subject:	Re: CR-LF handling behavior of SED changed recently - this breaks a lot of MinGW cross build scripts
To:	"cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
References:	<0F7D3B1B3C4B894D824F5B822E3E5A175B2636E4 AT IRSMSX103 DOT ger DOT corp DOT intel DOT com> <a53282b6-d00c-aad8-76a6-26b4089a9623 AT redhat DOT com> <0F7D3B1B3C4B894D824F5B822E3E5A175B26CE47 AT IRSMSX102 DOT ger DOT corp DOT intel DOT com> <59399CC5 DOT 60900 AT tlinx DOT org> <417f84ac-5d9f-dc50-e912-973e90b8a128 AT redhat DOT com> <0F7D3B1B3C4B894D824F5B822E3E5A175B26F278 AT IRSMSX102 DOT ger DOT corp DOT intel DOT com> <34b26965-34c2-b5f0-a3f2-b2c3df344b08 AT gmail DOT com> <0F7D3B1B3C4B894D824F5B822E3E5A175B270518 AT IRSMSX102 DOT ger DOT corp DOT intel DOT com>
From:	cyg Simple <cygsimple AT gmail DOT 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>
X-IsSubscribed:	yes

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

- Raw text -