From: "Morten Welinder" <mwelinder@gmail.com>
To: "Jörn Engel" <joern@logfs.org>
Cc: Pierre Habouzit <madcoder@debian.org>,
Johannes Berg <johannes@sipsolutions.net>,
linux-sparse@vger.kernel.org, 505177@bugs.debian.org
Subject: Re: Hard-coded gcc header path
Date: Tue, 11 Nov 2008 16:00:21 -0500 [thread overview]
Message-ID: <118833cc0811111300q4e7571f5o2a56a652f9a941e9@mail.gmail.com> (raw)
In-Reply-To: <20081111202849.GD25986@logfs.org>
The problem is not the header files, but that we need to ensure that the
proper include path is set up.
This is needed because sparse currently tries to mimic some
indeterminate gcc version in terms of predefines. A similar solution
would be needed to mimic any other compiler. We obviously need
a default path for system headers somehow.
In this case, we could probably get away with accepting a definition
of GCC_INTERNAL_INCLUDE on the command line and use that in
preference over whatever is in pre-process.h
Morten
next prev parent reply other threads:[~2008-11-11 21:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 13:58 Hard-coded gcc header path Jörn Engel
2008-11-11 14:01 ` Johannes Berg
2008-11-11 14:15 ` Jörn Engel
2008-11-11 20:13 ` Bug#505177: " Pierre Habouzit
2008-11-11 20:28 ` Jörn Engel
2008-11-11 21:00 ` Morten Welinder [this message]
2008-11-11 22:32 ` Jörn Engel
2008-11-11 23:10 ` Bernd Petrovitsch
2008-11-11 14:41 ` Bernd Petrovitsch
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=118833cc0811111300q4e7571f5o2a56a652f9a941e9@mail.gmail.com \
--to=mwelinder@gmail.com \
--cc=505177@bugs.debian.org \
--cc=joern@logfs.org \
--cc=johannes@sipsolutions.net \
--cc=linux-sparse@vger.kernel.org \
--cc=madcoder@debian.org \
/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 NNTP newsgroup(s).