On Tue, 2008-11-11 at 14:58 +0100, Jörn Engel wrote: > So why does sparse try 4.1.2 and not 4.1.3 or 4.3.2 or any other > variant? > joern@Galway:/usr/src/kernel/sparse$ cat pre-process.h > #define GCC_INTERNAL_INCLUDE "/usr/lib/gcc/i486-linux-gnu/4.1.2/include" > > Ah, it is hard-coding the path. Well, sort of. The patch is actually determined at sparse build time, so right now sparse requires you to build it against the same compiler that you are currently using. If you rebuild sparse with your shiny new compiler you'll notice that it'll end up with a different path in pre-process.h. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
