summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEric Blake <eblake@redhat.com>2012-09-06 08:20:17 -0600
committerEric Blake <eblake@redhat.com>2012-09-06 10:03:47 -0600
commit47fd706a7540e7ae3d19c625d90c28b88a8a640c (patch)
treed5d1950ceaba2be758d14bf0067bddd7ff6fdfc3
parenta514bc402cc5632e8986d55caeb49b664b6fe9e6 (diff)
downloadcoreutils-47fd706a7540e7ae3d19c625d90c28b88a8a640c.tar.gz
coreutils-47fd706a7540e7ae3d19c625d90c28b88a8a640c.tar.bz2
coreutils-47fd706a7540e7ae3d19c625d90c28b88a8a640c.zip
build: default to --enable-gcc-warnings for git tree
Anyone developing on coreutils can be assumed to have a new enough environment, such that enabling gcc warnings by default will be useful. Tarballs still default to no warnings, and the defaults can still be overridden with --disable-gcc-warnings. * configure.ac (gl_gcc_warnings): Set default based on environment. Suggested by Bernhard Voelker.
-rw-r--r--configure.ac6
1 files changed, 5 insertions, 1 deletions
diff --git a/configure.ac b/configure.ac
index d087c33b5..e1aa6caf1 100644
--- a/configure.ac
+++ b/configure.ac
@@ -75,7 +75,11 @@ AC_ARG_ENABLE([gcc-warnings],
*) AC_MSG_ERROR([bad value $enableval for gcc-warnings option]) ;;
esac
gl_gcc_warnings=$enableval],
- [gl_gcc_warnings=no]
+ [if test -d "$srcdir"/.git; then
+ gl_gcc_warnings=yes
+ else
+ gl_gcc_warnings=no
+ fi]
)
# gl_GCC_VERSION_IFELSE([major], [minor], [run-if-found], [run-if-not-found])