From: Alexey zaytsev <alexey.zaytsev@gmail.com>
To: Josh Triplett <josh@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-sparse@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>,
Josh Triplett <josh@freedesktop.org>
Subject: [PATCH 0/4] Proper gcc header dir handling in sparse.
Date: Mon, 08 Dec 2008 12:20:32 +0300 [thread overview]
Message-ID: <20081208091817.15890.27981.stgit@xl0.local> (raw)
[Resending with correct ml address. Sorry.]
Hello.
People have convinced me that sparse should take
gcc base directory as a run-time parameter, so it
could be used with gcc versions differing from the
one sparse was compiled with.
So here it goes, along with some related fixes.
The patches may also be pulled from
git://git.zaytsev.su/git/sparse.git git-base-dir
Also, the first two patches should fix the Debian bug 505177:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505177
---
Alexey zaytsev (4):
Set gcc include path at runtime.
Let cgcc pass -gcc-base-dir to sparse.
Document -gcc-base-dir in sparse.1
Rename dirafter to idirafter.
Makefile | 7 ++--
cgcc | 14 ++++++++
lib.c | 30 ++++++++++++-----
pre-process.c | 98 +++++++++++++++++++++++++++++++++++++++++++++------------
sparse.1 | 5 +++
5 files changed, 119 insertions(+), 35 deletions(-)
--
next reply other threads:[~2008-12-08 9:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 9:20 Alexey zaytsev [this message]
2008-12-08 9:20 ` [PATCH 1/4] Set gcc include path at runtime Alexey zaytsev
2008-12-09 10:08 ` Christoph Hellwig
2008-12-08 9:20 ` [PATCH 2/4] Let cgcc pass -gcc-base-dir to sparse Alexey zaytsev
2008-12-08 9:20 ` [PATCH 3/4] Document -gcc-base-dir in sparse.1 Alexey zaytsev
2008-12-08 9:21 ` [PATCH 4/4] Rename dirafter to idirafter Alexey zaytsev
2008-12-15 21:07 ` Sam Ravnborg
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=20081208091817.15890.27981.stgit@xl0.local \
--to=alexey.zaytsev@gmail.com \
--cc=hch@infradead.org \
--cc=josh@freedesktop.org \
--cc=josh@kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=sam@ravnborg.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).