From: "Lennart Sorensen" <lsorense@csclub.uwaterloo.ca>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
linux-kbuild@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>,
Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: Overriding -Werror
Date: Fri, 15 Aug 2014 11:33:53 -0400 [thread overview]
Message-ID: <20140815153353.GG17769@csclub.uwaterloo.ca> (raw)
In-Reply-To: <20140814222119.GD18411@ld-irv-0074>
On Thu, Aug 14, 2014 at 03:21:19PM -0700, Brian Norris wrote:
> I'm interested in being able to build-test kernels on various
> architectures while enabling extra warnings (make W=[123]). I'd like to
> be able to finish the builds and see all warnings, rather than seeing a
> failed build. However, GCC's -Werror is incompatible with this. There is
> plenty of code that will produce at least one warning, when warning
> verbosity is turned up. And GCC's -Werror is not guaranteed to remain
> stable over time; new versions may develop new warnings that may or may
> not be legitimate.
What ever is wrong with using '-k' with your make command?
--
Len Sorensen
next prev parent reply other threads:[~2014-08-15 15:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 22:21 Overriding -Werror Brian Norris
2014-08-15 9:30 ` Jeff Kirsher
2014-08-15 19:33 ` Brian Norris
2014-08-16 3:36 ` Mark D Rustad
2014-08-16 4:34 ` Brian Norris
2014-08-17 6:19 ` Mark D Rustad
2014-08-15 15:33 ` Lennart Sorensen [this message]
2014-08-15 16:51 ` Geert Uytterhoeven
2014-08-19 13:15 ` Andi Kleen
2014-08-19 18:43 ` Brian Norris
2014-08-19 20:11 ` Sam Ravnborg
2014-08-19 23:43 ` Andi Kleen
2014-08-20 5:10 ` 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=20140815153353.GG17769@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@linux-mips.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;
as well as URLs for NNTP newsgroup(s).