From: Roland Dreier <roland@topspin.com>
To: Pavel Machek <pavel@suse.cz>
Cc: torvalds@osdl.org, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: sparse refuses to work due to stdarg.h
Date: Mon, 17 Jan 2005 08:33:48 -0800 [thread overview]
Message-ID: <52oefogglv.fsf@topspin.com> (raw)
In-Reply-To: <20050117154626.GA16111@mars.ravnborg.org> (Sam Ravnborg's message of "Mon, 17 Jan 2005 16:46:26 +0100")
Sam> You seems to have a symlink? to /usr/include/asm in your
Sam> 3.3.5/include directory.
No, with debian gcc, /usr/lib/gcc-lib/i486-linux/3.3.5/include/asm/ is
a real directory that includes nothing but posix_types.h.
Sam> But real issue is search order of include paths in sparse.
Sam> sparse searches standard system dirs before dir's specified
Sam> with -I ... This in contradiction to 'info gcc - see
Sam> description for -I'.
Looks like you're right. On Debian, "make C=1 V=1" ends up with:
sparse -D__linux__ -Dlinux -D__STDC__ -Dunix -D__unix__ -nostdinc -isystem /usr/lib/gcc-lib/i486-linux/3.3.5/include -D__i386__ -Wp,-MD,init/.main.o.d -nostdinc -isystem /usr/lib/gcc-lib/i486-linux/3.3.5/include -D__KERNEL__ -Iinclude -Wall -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -ffreestanding -O2 -fomit-frame-pointer -pipe -msoft-float -mpreferred-stack-boundary=2 -march=i686 -mregparm=3 -Iinclude/asm-i386/mach-default -DKBUILD_BASENAME=main -DKBUILD_MODNAME=main init/main.c ;
/usr/lib/gcc-lib/i486-linux/3.3.5/include/asm/posix_types.h:29:35: warning: no newline at end of file
/usr/lib/gcc-lib/i486-linux/3.3.5/include/asm/posix_types.h:13:11: error: unable to open 'features.h'
so sparse is picking up the posix_types.h from the -isystem path
instead of the -I path as it should.
- Roland
prev parent reply other threads:[~2005-01-17 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-16 22:49 sparse refuses to work due to stdarg.h Pavel Machek
2005-01-17 4:49 ` Sam Ravnborg
2005-01-17 11:49 ` Pavel Machek
2005-01-17 15:46 ` Sam Ravnborg
2005-01-17 16:33 ` Roland Dreier [this message]
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=52oefogglv.fsf@topspin.com \
--to=roland@topspin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=torvalds@osdl.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