git: enable WARNS_WERROR by default

From:

Simon Schubert <corecode@xxxxxxxxxxxxxxxxxxxxxxx>

Date:

Wed, 16 Sep 2009 04:58:53 -0700 (PDT)

commit 18c2eecf34433a3e986bbd4b72fc03c800c47ac4
Author: Simon Schubert <corecode@dragonflybsd.org>
Date: Wed Sep 16 13:47:47 2009 +0200
enable WARNS_WERROR by default
This is to catch new warnings sneaking into buildworld. WARNS_WERROR
means that -Werror is added to sources iff compiled with WARNS >= 1.
All these sources have been fixed to currently compile without warnings.
Setting WARNS_WERROR helps us to maintain this status.
If your build should fail with a warning treated as error, you either
have introduced a new warning - in which case you will have to fix it
before committing - or you are using CFLAGS that exhibit warnings which
have not been fixed yet - in that case you should try and fix the
warning nevertheless.
*Only* if you are using compile flags which produce excess warnings, you
should disable WARNS_WERROR by setting NO_WERROR in make.conf. If you
do, make *absolutely* sure that you don't introduce new warnings into
the build, since it will break the build for everybody else who does not
set NO_WERROR!
Discussed-with: swildner@
Summary of changes:
etc/defaults/make.conf | 3 ++-
share/man/man5/make.conf.5 | 13 +++++++++++++
2 files changed, 15 insertions(+), 1 deletions(-)
http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/18c2eecf34433a3e986bbd4b72fc03c800c47ac4
--
DragonFly BSD source repository