linux-kernel - Re: [PATCH] kbuild: Fix passing -Wno-* options to gcc 4.4+

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:	Tue, 03 May 2011 10:52:27 +0200
From:	Michal Marek <mmarek@...e.cz>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	davej@...hat.com, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org, sam@...nborg.org
Subject: Re: [PATCH] kbuild: Fix passing -Wno-* options to gcc 4.4+

On 3.5.2011 02:44, Stephen Rothwell wrote:
> HI Michal,
>
> On Mon,  2 May 2011 14:13:01 +0200 Michal Marek<mmarek@...e.cz>  wrote:
>>
>> Starting with 4.4, gcc will happily accept -Wno-<anything>  in the
>> cc-option test and complain later when compiling a file that has some
>> other warning. This rather unexpected behavior is intentional as per
>> http://gcc.gnu.org/PR28322, so work around it by testing for support of
>> the opposite option (without the no-). Introduce a new Makefile function
>> cc-disable-warning that does this and update two uses of cc-option in
>> the toplevel Makefile.
>>
>> Reported-by: Stephen Rothwell<sfr@...b.auug.org.au>
>> Signed-off-by: Michal Marek<mmarek@...e.cz>
>
> This fixed things for me, thanks.
>
> Tested-by: Stephen Rothwell<sfr@...b.auug.org.au>

Thanks for spotting the warnings and for testing. I pushed this to 
kbuild-2.6.git#kbuild.

Michal
--
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/