From: Sam Ravnborg <sam@ravnborg.org>
To: Timur Tabi <timur.tabi@ammasso.com>
Cc: Christopher Li <lkml@chrisli.org>, linux-kernel@vger.kernel.org
Subject: Re: sparse error: unable to open 'stdarg.h'
Date: Wed, 18 May 2005 20:22:50 +0200 [thread overview]
Message-ID: <20050518182250.GB8130@mars.ravnborg.org> (raw)
In-Reply-To: <428B7143.4090607@ammasso.com>
On Wed, May 18, 2005 at 11:45:55AM -0500, Timur Tabi wrote:
> Christopher Li wrote:
>
> >I think I know that it is. There is a "-nostdinc" in the sparse
> >options, which I saw it in the other email you send out. It
> >drop the internal include path. Gcc is does the same thing.
> >
> >gcc -c -nostdinc /tmp/test.c
> >/tmp/test.c:1:22: no include path in which to find stdarg.h
>
> That option is set in the a_flags variable. I'm looking through the kbuild
> files (Makefile, etc) to see why a_flags is being used to build my driver.
Can you post a copy of you makefile. Then I may be able to tell you why.
Sam
next prev parent reply other threads:[~2005-05-18 18:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 21:46 Timur Tabi
2005-05-17 20:11 ` Christopher Li
2005-05-18 14:08 ` Timur Tabi
2005-05-18 12:38 ` Christopher Li
2005-05-18 15:51 ` Timur Tabi
2005-05-18 13:24 ` Christopher Li
2005-05-18 16:45 ` Timur Tabi
2005-05-18 18:22 ` Sam Ravnborg [this message]
2005-05-18 18:23 ` Timur Tabi
2005-05-20 19:37 ` Kbuild trick Sam Ravnborg
2005-05-20 23:43 ` Joel Becker
2005-05-21 5:12 ` Sam Ravnborg
2005-05-21 5:48 ` randy_dunlap
2005-05-21 20:41 ` Joel Becker
2005-05-21 10:59 ` Kedar Sovani
2005-05-22 7:28 ` Sam Ravnborg
2005-05-17 22:39 ` sparse error: unable to open 'stdarg.h' Timur Tabi
2005-05-18 18:22 ` Sam Ravnborg
2005-05-18 22:14 ` Timur Tabi
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=20050518182250.GB8130@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@chrisli.org \
--cc=timur.tabi@ammasso.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
all inboxes | Powered by JetHome®