linux-kernel - Re: [PATCH -v5] kbuild: Add extra gcc checks

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110309175625.GA29181@merkur.ravnborg.org>
Date:	Wed, 9 Mar 2011 18:56:25 +0100
From:	Sam Ravnborg <sam@...nborg.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Michal Marek <mmarek@...e.cz>, Borislav Petkov <bp@...en8.de>,
	Arnd Bergmann <arnd@...db.de>, torvalds@...ux-foundation.org,
	x86@...nel.org, linux-kernel@...r.kernel.org,
	linux-kbuild@...r.kernel.org, bp@...64.org
Subject: Re: [PATCH -v5] kbuild: Add extra gcc checks

> Another, related, very nice kbuild feature would be to allow for arch maintainers to 
> mark certain files as "should only build fine without warnings" - i.e. -Werror 
> should be the default. There would be a Kconfig feature to opt out of this, 
> CONFIG_CC_IGNORE_WARNINGS=y or so. This would allow for people to still build the 
> kernel with old (or buggy) versions of GCC.

To add -Werror for all files conditionally you can do:

    ccflags-$(CONFIG_WERROR) += -Werror

For individual files we can then drop -Werror like this:

    CFLAGS_REMOVE_foobar.o := -Werror

So it should be doable with the existing infrastructure.

	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/