From: Anthony Liguori <anthony@codemonkey.ws>
To: Jerone Young <jyoung5@us.ibm.com>
Cc: kvm-devel@lists.sourceforge.net, kvm-ppc-devel@lists.sourceforge.net
Subject: Re: [PATCH] Add -Werror to libkvm compile
Date: Mon, 24 Mar 2008 15:28:53 -0500 [thread overview]
Message-ID: <47E80F05.9030406@codemonkey.ws> (raw)
In-Reply-To: <e23a26d1da04a6dbb831.1206384270@thinkpadL>
Jerone Young wrote:
> # HG changeset patch
> # User Jerone Young <jyoung5@us.ibm.com>
> # Date 1206384205 18000
> # Branch merge
> # Node ID e23a26d1da04a6dbb831da7d03922abf95de7b30
> # Parent 972f62b6acae693c388d7b05d3a9ba7ef26ab4a0
> Add -Werror to libkvm compile
>
> This patch adds -Werror to CFLAGS for compilation of libkvm. This should stop complaints about Warnings.
>
What's unfortunate about -Werror is that GCC is notorious about
introducing warnings that aren't valid for particular versions of GCC.
While libkvm may compile with -Werror for you and may, there may be
existing (or future) versions of GCC that it won't build with whereas
the error being reported is not valid.
This is okay for developers, but not for users. In general, most
projects reserve -Werror for a developer or maintainer mode.
Regards,
Anthony Liguori
> Often I miss these warnings as they scroll right by with everything else during a big compile. This will help catch them.
>
> For qemu this using -Werror is not possible as a lot of qemu throw a gcc warning of some sort.
>
> Signed-off-by: Jerone Young <jyoung5@us.ibm.com>
>
> diff --git a/libkvm/Makefile b/libkvm/Makefile
> --- a/libkvm/Makefile
> +++ b/libkvm/Makefile
> @@ -11,6 +11,7 @@ CFLAGS += $(call cc-option, -fno-stack-p
> CFLAGS += $(call cc-option, -fno-stack-protector, "")
> CFLAGS += $(call cc-option, -fno-stack-protector-all, "")
> CFLAGS += -I $(KERNELDIR)/include
> +CFLAGS += -Werror
>
> LDFLAGS += $(CFLAGS)
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> kvm-devel mailing list
> kvm-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
prev parent reply other threads:[~2008-03-24 20:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 18:44 [PATCH] Add -Werror to libkvm compile Jerone Young
2008-03-24 19:42 ` [kvm-ppc-devel] " Segher Boessenkool
2008-03-25 16:33 ` Jerone Young
2008-03-25 17:08 ` Avi Kivity
2008-03-25 19:09 ` Jerone Young
2008-03-26 16:41 ` Avi Kivity
2008-03-24 20:28 ` Anthony Liguori [this message]
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=47E80F05.9030406@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=jyoung5@us.ibm.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=kvm-ppc-devel@lists.sourceforge.net \
/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