From: Sam Ravnborg <sam@ravnborg.org>
To: linux-kernel@vger.kernel.org
Subject: Re: sparse error: unable to open 'stdarg.h'
Date: Wed, 18 May 2005 20:22:17 +0200 [thread overview]
Message-ID: <20050518182217.GA8130@mars.ravnborg.org> (raw)
In-Reply-To: <428A729E.8040207@ammasso.com>
On Tue, May 17, 2005 at 05:39:26PM -0500, Timur Tabi wrote:
> Timur Tabi wrote:
>
> >make -C /lib/modules/2.6.8-24-smp/source
> >SUBDIRS=/root/AMSO1100/software/host/linux/sys/devccil C=1 V=2
>
> When I replace V=2 with V=1 (don't know how that happened), I get this
> output:
>
> sparse -D__i386__=1
> -Wp,-MD,/root/AMSO1100/software/host/linux/sys/devccil/.devnet.o.d
> -nostdinc -iwithprefix include -D__KERNEL__ -Iinclude -Wall
Newer kbuild's do not use the -nostdinc -iwithprefix include trick.
Instead they use -nostdinc -isystem `gcc --print-file-name=include`
Wich is a more reliable way to find stdarg.h. Newer sparse understands
this too.
Please post make V=1 output with a newer kernel.
Sam
next prev parent reply other threads:[~2005-05-18 18:21 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
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 [this message]
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=20050518182217.GA8130@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome