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=Itu4
	MIjAOLozUzX33c/+WG9vwd7yMB3N6Dibn67teqsL5cxiw2rb0kk4po9g0PTnay83
	E41xtKYqLZiyL7dEImEPfLUDSWQS4o4JLFFeOAemgWSL6TbZ2a73L3VfOtdD9dlM
	f6aGE4htkVqUphc2eHzZRGW+vr6zDwZtl4ZVjOM=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] [Updated] mingw64-{i686,x86_64} binutils, gcc (Test)
To: cygwin@cygwin.com
References: <33b5026b-7499-4a71-39c1-00629ed9cac8@gmail.com> <59c86185.48e6ca0a.964a0.a849@mx.google.com>
From: JonY <10walls@gmail.com>
Message-ID: <a339cc02-7fb0-1c5f-8e7c-d31056b974c5@gmail.com>
Date: Mon, 25 Sep 2017 14:17:28 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <59c86185.48e6ca0a.964a0.a849@mx.google.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="eqSGj4tQeddJDaHCMwkoFdJkVatQdREEG"

--eqSGj4tQeddJDaHCMwkoFdJkVatQdREEG
Content-Type: multipart/mixed; boundary="cCsKq7aN8TluGXwSQq7r76n9CpNfvonq6";
 protected-headers="v1"
From: JonY <10walls@gmail.com>
To: cygwin@cygwin.com
Message-ID: <a339cc02-7fb0-1c5f-8e7c-d31056b974c5@gmail.com>
Subject: Re: [ANNOUNCEMENT] [Updated] mingw64-{i686,x86_64} binutils, gcc
 (Test)
References: <33b5026b-7499-4a71-39c1-00629ed9cac8@gmail.com>
 <59c86185.48e6ca0a.964a0.a849@mx.google.com>
In-Reply-To: <59c86185.48e6ca0a.964a0.a849@mx.google.com>


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

On 09/25/2017 01:53 AM, Steven Penny wrote:
> 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.
>>
>> Unfortunately, I don't have any good ideas besides hacking cmake to
>> remove the -isystem calls, or contacting gcc-help directly.
>=20
> Here is another problem:
>=20
> $ cat z.cpp
> #include <iostream>
> main() {
> =C2=A0std::cout << "cout test\n";
> }
>=20
> $ x86_64-w64-mingw32-g++ -static -o z z.cpp
>=20
> $ ./z
> Segmentation fault

You can actually use Cygwin gdb to debug and see what went wrong,
assuming the debug symbols are around.

Sorry if I'm not much help, kind of busy these days.


--cCsKq7aN8TluGXwSQq7r76n9CpNfvonq6--

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

-----BEGIN PGP SIGNATURE-----

iQJGBAEBCAAwFiEE5QrdnbBX9Ppk4bbPcTtf4pwUXUUFAlnJD/kSHDEwd2FsbHNA
Z21haWwuY29tAAoJEHE7X+KcFF1F9N4P/RNjQ9cKsyxvnf5C0F0jwzygcnGvLmHk
+UdasrzCIc+TcR6f8oFmBJ0gncBauiKajVTUtAczLmIylCAGFn7R5kSu/7wWnAlk
dJ+ec27jQsvx1zOwW7K22Lmx7qK5YkgXeVpIZknQFn/2+1X2i+Gb3Ncild2RFOVj
Lkg4DMWTvg6RdeowrPt+vsl7hwD3CGpj7fyFfZ5nh11XaP/TJAwLD6EbEcxIjQ9X
r0Y+QWF1FPViyoWv9FFV/Xp+QBDvNLZTeTn5vi7/ko3jSeG/PBKRzwYJ8HY2mQWI
V1HrscK672WV731/Cb/6az0H2bAHVbNEzxUzz0CaA/OZ2dQPKGfMT00JCaoExVIQ
kwTQYHYpDwzG2/V+8ALBozufWvI4F3aiCfCzQm5suEGvr98jeRE3DgrqCmIm/ysq
u1BZ0GVT4pgVp/CH3WJVGdalnHXBAJyvr0BEaISN4OGXyaPT9c7HWVrO2cY/DpEj
cGlxQgrr5hxiSQLjFzqxzYqwh7I4tD6AECksHP6/CaIPYwI+tFzQ/hJLFn5hqnCf
t01Y7qGjCmrIG2yFGe70kdQbcIO9Um2rap41YoIzivL4xMS/T+B3LakBv3GxI0W7
iofa4oOKIwKK4I2j/QeTdzt5UEsFmwbk6AeUfKHv/eDyZdqaKF+bJUvvDu4QOA6f
OChavbmG4oD6
=i5BT
-----END PGP SIGNATURE-----

--eqSGj4tQeddJDaHCMwkoFdJkVatQdREEG--