public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: cc1: warning: ../../include/w32api: No such file or directory [enabled by default]
Date: Mon, 29 Jul 2013 16:58:00 -0000	[thread overview]
Message-ID: <87hafdmhur.fsf@Rainer.invalid> (raw)
In-Reply-To: <20130729124408.GE30069@calimero.vinschen.de>

Corinna Vinschen writes:
> It looks like this is a misbehaviour of gcc 4.7.3.  There are
> practically always non-existant default include dirs, not only on
> Cygwin.  If you try the same -Wmissing-include-dirs with gcc 4.8.1 on
> x86_64 Cygwin, there won't be such a warning.

I have no idea if that should be considered a bug or not, but the
combination "-Werror -Wmissing-include-dirs" is rendered useless due to
this.  Since it most assuredly doesn't point to a system path it uses
the current working directory instead in the final stage — so after
expansion the driver inserts a literal "-I ../../include/w32api", which
might silently pull in the wrong includes if the user happens to have
some directory like that.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada


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

  reply	other threads:[~2013-07-29 16:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-24 12:59 Achim Gratz
2013-07-29 12:44 ` Achim Gratz
2013-07-29 12:44   ` JonY
2013-07-29 13:42     ` Corinna Vinschen
2013-07-29 13:36   ` Corinna Vinschen
2013-07-29 16:58     ` Achim Gratz [this message]
2014-02-28 20:54 Peter Rosin
2014-02-28 21:50 ` Andrey Repin

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=87hafdmhur.fsf@Rainer.invalid \
    --to=stromeko@nexgo.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).