linux-kernel - Re: [2.6.24-rc2] make C=1 killed by sparse 0.4 choking on kernel/sched.c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20071113114135.GA30627@uranus.ravnborg.org>
Date:	Tue, 13 Nov 2007 12:41:35 +0100
From:	Sam Ravnborg <sam@...nborg.org>
To:	Tilman Schmidt <tilman@...p.cc>
Cc:	linux-kernel@...r.kernel.org, josh@...edesktop.org
Subject: Re: [2.6.24-rc2] make C=1 killed by sparse 0.4 choking on kernel/sched.c

> 
> I don't quite know what to make of this. It looks like a bug in
> sparse, but kernel/sched.c is perhaps not quite innocent either.
> Also it doesn't seem right that the entire kernel compilation
> aborts just because of a failed sparse run.
> 
> Opinions?

With "make C=1" you can always do "make kernel/sched.o"
And then continue with "make C=1"

It is on purpose it stops so you are forced to fix your bugs.
It is not designed with sparse errors in mind :-)

	Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/