qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Mark McLoughlin <markmc@redhat.com>
Cc: Paul Brook <paul@codesourcery.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC] Enable Werrror by default
Date: Thu, 11 Jun 2009 13:30:05 -0500	[thread overview]
Message-ID: <4A314D2D.2060505@codemonkey.ws> (raw)
In-Reply-To: <1244726086.7752.25.camel@blaa>

[-- Attachment #1: Type: text/plain, Size: 1326 bytes --]

Mark McLoughlin wrote:
> On Thu, 2009-06-11 at 13:35 +0100, Paul Brook wrote:
>
>   
>> I'd like to enable Werror by default. I've been using --enable-werror locally 
>> for a while now, and it's been extremely useful in picking up dumb errors 
>> (like the recent stellaris_enet.c breakage).
>>
>> Any objections?
>>
>> You can of course configure with --disable-werror if you really want the force 
>> things to build.
>>     
>
> Based on experiences with other projects:
>
>   1) Release tarballs should not ship with -Werror on by default - e.g. 
>      new gcc comes along with new warnings and the tarball build fails 
>      with no benefit to anyone
>
>   2) Anyone submitting patches should build with -Werror and make sure 
>      they don't introduce new warnings
>
>   3) People with newer gcc are likely to be tripped up by warnings 
>      introduced by others with older gcc[1]
>
>   4) It's debatable whether builds from git should default to -Werror - 
>      on the plus side it helps ensure (2) happens, on the minus side if 
>      a warning does sneak in, it makes life a pain for everyone until a 
>      fix gets applied
>
> IMHO, we should enable it by default for git builds.
>   
How about the following?  It currently only enables werror for Linux 
hosts and git builds.

Regards,

Anthony Liguori

[-- Attachment #2: enable-werror.patch --]
[-- Type: text/x-patch, Size: 1237 bytes --]

commit ba59b4615be2b9b989b425bad2499f47a6928d5c
Author: Anthony Liguori <aliguori@us.ibm.com>
Date:   Thu Jun 11 13:28:25 2009 -0500

    Enable -Werror by default for git builds on Linux hosts
    
    Additional hosts can be added to the white list as they are confirmed to build
    with --enable-werror.
    
    Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>

diff --git a/configure b/configure
index 89e7f53..48c8949 100755
--- a/configure
+++ b/configure
@@ -356,11 +356,7 @@ else
 fi
 [ -f "$workdir/vl.c" ] || source_path_used="yes"
 
-werror="no"
-# generate compile errors on warnings for development builds
-#if grep cvs $source_path/VERSION > /dev/null 2>&1 ; then
-#werror="yes";
-#fi
+werror=""
 
 for opt do
   optarg=`expr "x$opt" : 'x[^=]*=\(.*\)'`
@@ -657,6 +653,18 @@ if test ! -x "$(which cgcc 2>/dev/null)"; then
     sparse="no"
 fi
 
+# Consult white-list to determine whether to enable werror
+# by default.  Only enable by default for git builds
+if test -z "$werror" ; then
+    z_version=`cut -f3 -d. $source_path/VERSION`
+    if test "$z_version" = "50" -a \
+       "$linux" = "yes" ; then
+	werror="yes"
+    else
+	werror="no"
+    fi
+fi
+
 #
 # Solaris specific configure tool chain decisions
 #

  parent reply	other threads:[~2009-06-11 18:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-11 12:35 [Qemu-devel] [RFC] Enable Werrror by default Paul Brook
2009-06-11 12:46 ` Tristan Gingold
2009-06-11 13:10   ` Christoph Egger
2009-06-11 14:02   ` Andreas Färber
2009-06-11 12:58 ` Anthony Liguori
2009-06-11 13:14 ` Mark McLoughlin
2009-06-11 13:34   ` Christoph Egger
2009-06-11 13:35   ` Paul Brook
2009-06-11 14:20   ` Richard W.M. Jones
2009-06-11 18:30   ` Anthony Liguori [this message]
2009-06-11 18:38     ` Mark McLoughlin
2009-06-11 20:03       ` Anthony Liguori
2009-06-11 22:28     ` Paul Brook
2009-06-11 15:18 ` David Turner
2009-06-11 17:24   ` Stuart Brady

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=4A314D2D.2060505@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=markmc@redhat.com \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.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).