From: Michal Marek <mmarek@suse.cz>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: davej@redhat.com, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, sam@ravnborg.org
Subject: Re: [PATCH] kbuild: Fix passing -Wno-* options to gcc 4.4+
Date: Tue, 03 May 2011 10:52:27 +0200 [thread overview]
Message-ID: <4DBFC24B.7090805@suse.cz> (raw)
In-Reply-To: <20110503104440.700ea26f.sfr@canb.auug.org.au>
On 3.5.2011 02:44, Stephen Rothwell wrote:
> HI Michal,
>
> On Mon, 2 May 2011 14:13:01 +0200 Michal Marek<mmarek@suse.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@canb.auug.org.au>
>> Signed-off-by: Michal Marek<mmarek@suse.cz>
>
> This fixed things for me, thanks.
>
> Tested-by: Stephen Rothwell<sfr@canb.auug.org.au>
Thanks for spotting the warnings and for testing. I pushed this to
kbuild-2.6.git#kbuild.
Michal
next prev parent reply other threads:[~2011-05-03 8:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 2:18 linux-next: build warning after merge of the kbuild tree Stephen Rothwell
2011-05-02 2:24 ` Dave Jones
2011-05-02 3:45 ` Stephen Rothwell
2011-05-02 4:02 ` Dave Jones
2011-05-02 4:44 ` Stephen Rothwell
2011-05-02 4:24 ` Stephen Rothwell
2011-05-02 4:36 ` Dave Jones
2011-05-02 5:57 ` Stephen Rothwell
2011-05-02 4:53 ` Stephen Rothwell
2011-05-02 11:13 ` Michal Marek
2011-05-02 12:13 ` [PATCH] kbuild: Fix passing -Wno-* options to gcc 4.4+ Michal Marek
2011-05-03 0:44 ` Stephen Rothwell
2011-05-03 8:52 ` Michal Marek [this message]
2011-05-02 15:17 ` linux-next: build warning after merge of the kbuild tree Valdis.Kletnieks
2011-05-02 15:31 ` Michal Marek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DBFC24B.7090805@suse.cz \
--to=mmarek@suse.cz \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).