From: Sam Ravnborg <sam@ravnborg.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: torvalds@transmeta.com, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: sparse refuses to work due to stdarg.h
Date: Mon, 17 Jan 2005 05:49:55 +0100 [thread overview]
Message-ID: <20050117044955.GA8092@mars.ravnborg.org> (raw)
In-Reply-To: <20050116224922.GA4454@elf.ucw.cz>
On Sun, Jan 16, 2005 at 11:49:22PM +0100, Pavel Machek wrote:
> Hi!
>
> I'm probably doing something wrong, but... how do I force it to work?
> I'm pretty sure it worked before, I'm not sure what changed in my
> config.
kbuild was changed to reliably pick up the stdarg.h for the gcc used.
Two issues has popped up:
1) sparse did not support -isystem dir
- fixed a few days ago, and fix is at sparse.bkbits.net
2) misconfigured gcc's that report a wrong directory when using
gcc -print-file-name=include
The directory given must include stdarg.h - otherwise gcc config is
broken.
You are hit by 1)
Sam
next prev parent reply other threads:[~2005-01-17 4:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-16 22:49 sparse refuses to work due to stdarg.h Pavel Machek
2005-01-17 4:49 ` Sam Ravnborg [this message]
2005-01-17 11:49 ` Pavel Machek
2005-01-17 15:46 ` Sam Ravnborg
2005-01-17 16:33 ` Roland Dreier
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=20050117044955.GA8092@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=torvalds@transmeta.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