From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] [Updated] mingw64-{i686,x86_64} binutils, gcc (Test)
Date: Mon, 25 Sep 2017 16:43:00 -0000 [thread overview]
Message-ID: <c243203f-5551-3b11-02d7-4fd35edc4835@t-online.de> (raw)
In-Reply-To: <59c86185.48e6ca0a.964a0.a849@mx.google.com>
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
next prev parent reply other threads:[~2017-09-25 16:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-20 16:19 JonY
2017-08-21 1:57 ` Steven Penny
2017-08-21 2:45 ` Steven Penny
2017-08-22 2:22 ` Steven Penny
2017-08-22 12:47 ` JonY
2017-09-19 23:14 ` Steven Penny
2017-09-21 0:10 ` Steven Penny
2017-09-24 0:49 ` JonY
2017-09-24 3:07 ` Steven Penny
2017-09-25 1:53 ` Steven Penny
2017-09-25 14:18 ` JonY
2017-09-25 18:33 ` Steven Penny
2017-09-27 23:43 ` JonY
2017-09-28 4:13 ` Steven Penny
2017-09-25 16:43 ` Hans-Bernhard Bröker [this message]
2017-09-25 18:44 ` Steven Penny
2017-09-25 20:04 ` Hans-Bernhard Bröker
2017-09-27 4:35 ` Andrey Repin
2017-10-17 11:47 ` Steven Penny
2017-10-18 7:30 ` JonY
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c243203f-5551-3b11-02d7-4fd35edc4835@t-online.de \
--to=hbbroeker@t-online.de \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).