On Tue, Aug 26, 2008 at 10:44 AM, Bernd Petrovitsch <bernd@xxxxxxxxx> wrote: > I (obviously) don't know any details about your situation but do you > have any specific reason that you have different sets of -I/-D > parameters on dependency generation and the real compile run? To put a long story short: I run sparse against netbsd tree. To be slightly more elaborate, I should mention that I wasn't able so far to fully appreciate the beauty and elegance of certain design decisions of the project in question. Nevertheless, I'm seeing different reports from gendep and compilation runs. > Personally I see only subtle problems on the horizon with such a > situation. > Let alone that it is somewhat simpler to have *one* CFLAGS/CPPFLAGS/... > variable and use that everywhere. Well, that aside, the overall build time significantly increases with having to run sparse twice. Same warnings/errors are reported twice. I still think that sparse has no business validating any code when cgcc is called in -M mode; all those files are going to be compiled later on anyway. And it's the compilation stage where warnings are desirable. Regards, -- Alex -- 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
