On Mon, 2008-02-25 at 09:54 +0100, Pierre Habouzit wrote: > > Perhaps a simpler approach would be to turn off warnings in any files > > included using angle brackets. > > Nope, that's not good, because I use angle brackets to #include files > from my projects when I use internally in-tree headers that will in the > end be public. > > I'd rather like to ask to ignore warnings for example, for file under > /usr/include and /usr/lib/gcc/ You are right. I think sparse should try to follow gcc in this regard. There are three hardcoded directories in pre-process.c (/usr/include, /usr/local/include and the gcc include directory). Maybe they should be considered system include directories. -- Regards, Pavel Roskin - To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
