Message-ID: <428B7143.4090607@ammasso.com>
Date: Wed, 18 May 2005 11:45:55 -0500
From: Timur Tabi <timur.tabi@ammasso.com>
Organization: Ammasso
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217 Mnenhy/0.7.2.0
MIME-Version: 1.0
To: Christopher Li <lkml@chrisli.org>
CC: linux-kernel@vger.kernel.org
Subject: Re: sparse error: unable to open 'stdarg.h'
References: <428A661C.1030100@ammasso.com> <20050517201148.GA12997@64m.dyndns.org> <428B4C67.5090307@ammasso.com> <20050518123854.GA13452@64m.dyndns.org> <428B646C.3030501@ammasso.com> <20050518132417.GA14488@64m.dyndns.org>
In-Reply-To: <20050518132417.GA14488@64m.dyndns.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1005
Lines: 28

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.

As far as I'm concerned, this is a bug in kbuild, and I think it only shows up with 
external modules.

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