From: JonY <10walls@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] [Updated] mingw64-{i686,x86_64} binutils, gcc (Test)
Date: Sun, 24 Sep 2017 00:49:00 -0000 [thread overview]
Message-ID: <33b5026b-7499-4a71-39c1-00629ed9cac8@gmail.com> (raw)
In-Reply-To: <59c3037d.4cfdca0a.795e7.29d7@mx.google.com>
[-- Attachment #1.1: Type: text/plain, Size: 1510 bytes --]
On 09/21/2017 12:10 AM, Steven Penny wrote:
>
> $ x86_64-w64-mingw32-g++ \
>> -isystem /usr/x86_64-w64-mingw32/sys-root/mingw/include alfa.cpp
> In file included from
> /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/ext/string_conversions.h:41:0,
>
> from
> /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/bits/basic_string.h:5402,
> from /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/string:52,
> from /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/stdexcept:39,
> from /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/array:39,
> from /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/tuple:39,
> from /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/functional:55,
> from alfa.cpp:2:
> /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/cstdlib:75:25: fatal
> error:
> stdlib.h: No such file or directory
> #include_next <stdlib.h>
>
> Now really "-I" and "-isystem" are not really needed for this example,
> because
> that directory gets pulled in already - but it should work even with them
> included. Also it is somewhat important that it do work even with the
> redundant
> options included, because Cmake often dumps those options in with GCC
> commands.
>
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.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 858 bytes --]
next prev parent reply other threads:[~2017-09-24 0:49 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 [this message]
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
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=33b5026b-7499-4a71-39c1-00629ed9cac8@gmail.com \
--to=10walls@gmail.com \
--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).