diff options
| author | Lubomir Rintel <lkundrak@v3.sk> | 2015-05-17 20:49:06 +0200 |
|---|---|---|
| committer | Lubomir Rintel <lkundrak@v3.sk> | 2015-06-02 12:30:03 +0200 |
| commit | 30e903489430d7b90fabb82eb3bc21b8c41dcbc0 (patch) | |
| tree | b0436c981065d176096a2980a113b3e2930819b5 /m4 | |
| parent | fbd24d1073f16b90d4819d920102e3011b605e4e (diff) | |
build: don't default to -Werror
It seems like a poor default for various downstream toolchains. We can't
anticipate the compiler warnings for future compiler versions and older
ones are prone to false positives. Also, older gdbus-codegen is known
to generate code that triggers compiler warnings.
Let's keep it enabled for maintainer builds and distcheck so that we're
sure a tool chain that builds releases without warnings exists.
Diffstat (limited to 'm4')
| -rw-r--r-- | m4/compiler_warnings.m4 | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/m4/compiler_warnings.m4 b/m4/compiler_warnings.m4 index 5c8d20777..a1c4e1288 100644 --- a/m4/compiler_warnings.m4 +++ b/m4/compiler_warnings.m4 @@ -22,7 +22,7 @@ AC_DEFUN([NM_COMPILER_WARNING], [ AC_DEFUN([NM_COMPILER_WARNINGS], [AC_ARG_ENABLE(more-warnings, AS_HELP_STRING([--enable-more-warnings], [Possible values: no/yes/error]), - set_more_warnings="$enableval",set_more_warnings=error) + set_more_warnings="$enableval",set_more_warnings=yes) AC_MSG_CHECKING(for more warnings) if test "$GCC" = "yes" -a "$set_more_warnings" != "no"; then AC_MSG_RESULT(yes) |