On Mon, 17 Jan 2005, Sam Ravnborg wrote:
>
> You seems to have a symlink? to /usr/include/asm in your 3.3.5/include
> directory.
> But real issue is search order of include paths in sparse.
> sparse searches standard system dirs before dir's specified with -I ...
> This in contradiction to 'info gcc - see description for -I'.
I don't do info-files (what a stupid idea they are - before html they were
detrimental as they caused normal man-pages to be useless, and after html
they have no reason for existence what-so-ever).
Is the gcc logic documented somewhere? Ie what are the relevant rules for
-I, -isystem, -iprefix, -idirafter etc, and how do they interact with
#include "file.h"
#include <file.h>
The sparse logic itself is pretty simple: I know gcc has this stupid
notion of two separate include-paths, and sparse used to do that too, but
it sucked so bad with "#include_next" that it's now just one include-path,
but it has a couple of "marker pointers" that get updated to show where
the "system" headers start and where the "normal" headers are..
So it's not like I can't make sparse do anything I like, but the gcc
behaviour is so confusing that...
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
