Re: sparse error: unable to open 'stdarg.h'

[Sam Ravnborg]

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/