From: Eric Dumazet <eric.dumazet@gmail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Michal Marek <mmarek@suse.cz>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
Dave Jones <davej@redhat.com>
Subject: Re: [PATCH] kbuild: fix W=1 with gcc 4.3.2
Date: Thu, 21 Apr 2011 23:13:23 +0200 [thread overview]
Message-ID: <1303420403.2784.25.camel@edumazet-laptop> (raw)
In-Reply-To: <20110421210852.GA6196@merkur.ravnborg.org>
Le jeudi 21 avril 2011 à 23:08 +0200, Sam Ravnborg a écrit :
> Building a kernel using W=1 with gcc 4.3.2 failed like this:
>
> cc1: error: unrecognized command line option "-Wpacked-bitfield-compat"
>
> Make use of this option dependent on the compiler.
>
> Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
> Cc: Dave Jones <davej@redhat.com>
> ---
> I do not see this a stable material - people running stable kernels
> have less value of W=1.
>
> And the amount of warnings are outright silly. We should really
> divide this up a bit so W=1 is semi usefull.
>
> Sam
>
> diff --git a/scripts/Makefile.build b/scripts/Makefile.build
> index d5f925a..b280284 100644
> --- a/scripts/Makefile.build
> +++ b/scripts/Makefile.build
> @@ -73,7 +73,7 @@ KBUILD_EXTRA_WARNINGS += -Wnested-externs
> KBUILD_EXTRA_WARNINGS += -Wold-style-definition
> KBUILD_EXTRA_WARNINGS += $(call cc-option, -Woverlength-strings,)
> KBUILD_EXTRA_WARNINGS += -Wpacked
> -KBUILD_EXTRA_WARNINGS += -Wpacked-bitfield-compat
> +KBUILD_EXTRA_WARNINGS += $(call cc-option, -Wpacked-bitfield-compat)
> KBUILD_EXTRA_WARNINGS += -Wpadded
> KBUILD_EXTRA_WARNINGS += -Wpointer-arith
> KBUILD_EXTRA_WARNINGS += -Wredundant-decls
> --
Please add same fix for gcc-4.1.2
cc1: error: unrecognized command line option "-Wlogical-op"
next prev parent reply other threads:[~2011-04-21 21:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 21:08 Sam Ravnborg
2011-04-21 21:13 ` Eric Dumazet [this message]
2011-04-21 21:17 ` Joe Perches
2011-04-21 21:31 ` [PATCH] kbuild: fix W=1 with gcc 4.1.2 / 4.3.2 Sam Ravnborg
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=1303420403.2784.25.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=davej@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sam@ravnborg.org \
/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
all inboxes | Powered by JetHome®