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

[Timur Tabi <timur.tabi@ammasso.com>]

Christopher Li wrote:

> That is wired.  Can you try to edit a test.c contain just one line:
> 
> #include <stdarg.h>
> 
> run sparse on that test.c and see if you get any complain or not?

I did "sparse test.c" and got no output whatsoever.  No files were created, either.

> 
> If you still get complain about file not found. Can you run
> "strace -e trace=file ./check test.c" and show me the out put?

I get the same thing:

execve("sparse-bk/check", ["sparse-bk/check", "test.c"], [/* 57 vars */]) = 0
access("/etc/ld.so.preload", R_OK)      = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY)      = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=74426, ...}) = 0
open("/lib/tls/libc.so.6", O_RDONLY)    = 3
fstat64(3, {st_mode=S_IFREG|0755, st_size=1359489, ...}) = 0
open("test.c", O_RDONLY)                = 3
open("/usr/include/stdarg.h", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/local/include/stdarg.h", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/lib/gcc-lib/i586-suse-linux/3.3.4/include/stdarg.h", O_RDONLY) = 3

There must be something specific about how kbuild calls sparse.

-- 
Timur Tabi
Staff Software Engineer
timur.tabi@ammasso.com

One thing a Southern boy will never say is,
"I don't think duct tape will fix it."
      -- Ed Smylie, NASA engineer for Apollo 13