From: Steven Penny <svnpenn@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] [Updated] mingw64-{i686,x86_64} binutils, gcc (Test)
Date: Tue, 19 Sep 2017 23:14:00 -0000 [thread overview]
Message-ID: <59c1a4d8.072d9d0a.f9f88.5663@mx.google.com> (raw)
In-Reply-To: <63d39593-2806-a913-487a-02b93ae1fd1d@gmail.com>
On Tue, 22 Aug 2017 12:47:08, JonY wrote:
> On 08/22/2017 02:21 AM, Steven Penny wrote:
> > stdlib.h: No such file or directory
> > #include_next <stdlib.h>
> >=20
>
> Seems to be working for me on a minimalist test case. Can you show your
> command line and run g++ with -v?
http://cygwin.com/ml/cygwin/2017-08/msg00193.html
Looks like a Cmake error rather than GCC - thought you might like to know. Cmake
is inserting "-isystem" instead of "-I":
http://github.com/Martchus/tageditor/issues/22#issuecomment-330698400
Side note, our Cmake is now over a year old - but I will post that in separate
thread - thanks
--
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-19 23:14 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 [this message]
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
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=59c1a4d8.072d9d0a.f9f88.5663@mx.google.com \
--to=svnpenn@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).