linux-kernel - Re: problem with ccflags := -Werror in Makefiles when building with gcc 4.6.0

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]

Date:	Wed, 9 Mar 2011 19:00:37 +0100
From:	Sam Ravnborg <sam@...nborg.org>
To:	Joe Perches <joe@...ches.com>
Cc:	Douglas Mencken <dougmencken@...il.com>,
	linux-kernel@...r.kernel.org, Borislav Petkov <bp@...en8.de>,
	Michal Marek <mmarek@...e.cz>, Ingo Molnar <mingo@...e.hu>,
	linux-kbuild <linux-kbuild@...r.kernel.org>
Subject: Re: problem with ccflags := -Werror in Makefiles when building
	with gcc 4.6.0

On Wed, Mar 09, 2011 at 09:22:50AM -0800, Joe Perches wrote:
> On Wed, 2011-03-09 at 17:28 +0100, Douglas Mencken wrote:
> > When building with gcc 4.6.0 with the new type of warnings introduced,
> > -Wunused-but-set-variable, many directories with ccflags set to
> > -Werror in Makefile fail to build.
> 
> After the kbuild W=<level> gets accepted,
> it might be reasonable to add another W
> level to make warnings fatal and remove
> all -Werror entries from the various Makefiles.

It does not make sense to remove -Werror.
They are there by default.

It is just plain wrong to go removing -Werror that has been there for ages.
Either we fix the warnings or we tell gcc to shut up.

	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/