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=FbFkKMK7HIKQiHpu
	akWYIgthTNJIGqObvB7lVXsMQtXZi6gJcfGvKywV7ZjVcSs2qRR8uy48D5CNB/P/
	651AnQwayrnmiXz1yPS6TkAhokrULm9WSRQRG7Jm0HhsDuy6wI27zGhSka6TcnHQ
	HZB899ss5EoU94UfxKkToVXoqIE=
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=IBQ9Rv24xxZ3dUHsrj2wWr
	rt6sE=; b=VpQg4sqG5YD98EVNQTzNVkpmUZwFEYf/TTaZiU+9Hs8HfodIN8dAiU
	ltyHW8U0dkIAIiuoxj4pwH6gfe9xiUjJ7hx7/RlSVGMZ/AvSsNKOxgAqlDy6mRv2
	+zK669Oh8ly+2itEI9sIm3SFBRcg3P+ayrkF+eLb4bZEQo7Mtos6M=
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=0.4 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD autolearn=no version=3.3.2 spammy=H*M:online, H*F:D*t-online.de, among, HContent-Transfer-Encoding:8bit
X-HELO:	mailout12.t-online.de
Subject:	Re: [ANNOUNCEMENT] [Updated] mingw64-{i686,x86_64} binutils, gcc (Test)
To:	cygwin AT cygwin DOT com
References:	<33b5026b-7499-4a71-39c1-00629ed9cac8 AT gmail DOT com> <59c86185 DOT 48e6ca0a DOT 964a0 DOT a849 AT mx DOT google DOT com>
From:	=?UTF-8?Q?Hans-Bernhard_Br=c3=b6ker?= <HBBroeker AT t-online DOT de>
Message-ID:	<c243203f-5551-3b11-02d7-4fd35edc4835@t-online.de>
Date:	Mon, 25 Sep 2017 18:43:27 +0200
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version:	1.0
In-Reply-To:	<59c86185.48e6ca0a.964a0.a849@mx.google.com>
X-IsSubscribed:	yes

Am 25.09.2017 um 03:53 schrieb Steven Penny:
> On Sun, 24 Sep 2017 00:48:20, JonY wrote:
>> I don't really work with cmake, but what it looks like, but it probably
>> makes gcc look in the mingw include dir first and then gcc's, breaking
>> gcc's headers.

Correct thus far.  -isystem is really not a compiler option that CMake 
should be injecting on its own recognizance.  It's for specs files, 
compiler/libc implementation control and such.  It will almost certainly 
break, among other things, any non-trivial use of #include_next.

> Here is another problem:
> 
> $ cat z.cpp
> #include <iostream>
> main() {
>   std::cout << "cout test\n";
> }
> 
> $ x86_64-w64-mingw32-g++ -static -o z z.cpp
> 
> $ ./z
> Segmentation fault

Does not reproduce here.


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