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 12:44:00 -0000	[thread overview]
Message-ID: <loom.20130729T141755-373@post.gmane.org> (raw)
In-Reply-To: <loom.20130724T131352-6@post.gmane.org>

Achim Gratz <Stromeko <at> NexGo.DE> writes:
> The above warning appears when -Wmissing-include-dirs is in effect (and
> aborts compilation if -Werror is also given).  The missing include path
> seems to be produced by the following compiler spec:
> 
> %(cpp_cpu) [...] %{!nostdinc:%{!mno-win32:-idirafter ../include/w32api%s
> -idirafter ../../include/w32api%s}}
> 
> which gets expanded into
> 
> -idirafter /usr/lib/gcc/i686-pc-cygwin/4.7.3/../../../../include/w32api
> -idirafter ../../include/w32api

If I crate a link /usr/include -> /include then the warning / error is not
produced.  Since I don't think /include is supposed to exist on Cygwin, it
seems the compiler spec is wrong?


Regards,
Achim.




--
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 12:19 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 [this message]
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
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=loom.20130729T141755-373@post.gmane.org \
    --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).