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; q=dns; s=default; b=k4u7
	3nWKUkJYRNTRwSNriPQTE+GDci8VHzbvI1x4HnfE78pBpCyz895AZCaZ/rfjnyOG
	WSes4aHF/NRrkGG18zSTmjW/CuBeAZRPc2XtTWB7tfQdoV1WQMcBWGAVVI6ov3Rn
	qRinWZNYpZqaPa1tB8N5vq74iZVu9WvbsKoD2/A=
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; s=default; bh=b4Mf4Wrv3e
	hitTrFdiySrTJJKsA=; b=XvXmx6E5Yzth5b0c8Mebyst27hOAFuHmncbgQGUspU
	4PhdZcyvAb5tl4mavE/zuWYdzPpHUNpqajgcZ4uI6FqGK8RJJ4hdNoZ5qlDZo6S8
	v0Uwbd4n2r69lLuPpvJn3yrH+atbVDUTzMTbVzD1wG9G6rRGCGCreAt7jZlpv4vD
	g=
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=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=H*c:application
X-HELO: mx1.redhat.com
DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 710B480B29
Authentication-Results: ext-mx04.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
Authentication-Results: ext-mx04.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=eblake AT redhat DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 710B480B29
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
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> <5313de97-d9bd-d9c9-cb4a-254a3eadcf4a AT redhat DOT com> <dfe98b04-27cf-af72-5e96-7a65460c1e53 AT gmail DOT com>
From: Eric Blake <eblake AT redhat DOT com>
Openpgp: url=http://people.redhat.com/eblake/eblake.gpg
Message-ID: <3100fec0-bed0-f2fd-fe3c-11e5580d80f0@redhat.com>
Date: Sat, 10 Jun 2017 21:30:26 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0
MIME-Version: 1.0
In-Reply-To: <dfe98b04-27cf-af72-5e96-7a65460c1e53@gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ACwkSmbh6VRDSRsrEkeb6hKcFI3HVEcAC"
X-IsSubscribed: yes

--ACwkSmbh6VRDSRsrEkeb6hKcFI3HVEcAC
Content-Type: multipart/mixed; boundary="moR60vxIcasmXbCOrUuSsOMQxWHxCU9tp";
 protected-headers="v1"
From: Eric Blake <eblake AT redhat DOT com>
To: cygwin AT cygwin DOT com
Message-ID: <3100fec0-bed0-f2fd-fe3c-11e5580d80f0 AT redhat DOT com>
Subject: Re: CR-LF handling behavior of SED changed recently - this breaks a
 lot of MinGW cross build scripts
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>
 <5313de97-d9bd-d9c9-cb4a-254a3eadcf4a AT redhat DOT com>
 <dfe98b04-27cf-af72-5e96-7a65460c1e53 AT gmail DOT com>
In-Reply-To: <dfe98b04-27cf-af72-5e96-7a65460c1e53 AT gmail DOT com>


--moR60vxIcasmXbCOrUuSsOMQxWHxCU9tp
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 06/10/2017 08:48 AM, cyg Simple wrote:

>=20
> Uhm, 'wt' and 'wb' came from MS itself.

Not quite. fopen(,"wb") comes from POSIX.  "wb" is probably a microsoft
extension, but it is certainly not in POSIX nor in glibc.

>  GNU GCC was adapted to allow it

Huh? It's not whether the compiler allows it, but whether libc allows
it.  ALL libc that are remotely close to POSIX compliant support
fopen(,"wb"), but only Windows platforms (and NOT glibc) support
fopen(,"wt").

--=20
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org


--moR60vxIcasmXbCOrUuSsOMQxWHxCU9tp--

--ACwkSmbh6VRDSRsrEkeb6hKcFI3HVEcAC
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Public key at http://people.redhat.com/eblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCAAGBQJZPKtCAAoJEKeha0olJ0Nq+1EH/0h7aP8XBtoqT5DjoYvZ6toL
g/N4WIMW+CHwI+aDMQ1iABBc59sQUjDJE22pEc1RyCuiLbIfcZsS7IYRSFA+NAqR
yETV02WSmWwxP6cym9TRRpTxoJaf8M5NDdxaP5dgySvYUzGON2p8ClLspO6gY4IU
ROWj1XxW1FvOZqHT5fOsWaitRr8p6mt4wymxDDox6/eBAKgRLWU7WXZtIw45TmfU
+q90Czl7ltvR5HSfFqjM82gPhKOm7cM2JKLjP1A5d8hDU982OOxsRC/shR4cSS6X
R/RL7m4OsUAR+msGSQhQlB4kaF6wZcHvb4d0jKYmjVkwvrOA3ZyY/TpKeuYy2OU=
=nHLy
-----END PGP SIGNATURE-----

--ACwkSmbh6VRDSRsrEkeb6hKcFI3HVEcAC--