grep branch, master, updated. v2.14-10-gefa477a

[Jim Meyering]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "grep".

The branch, master has been updated
       via  efa477a2c147c60480ae0de323fd8c50aee4df6e (commit)
      from  f97be96b2dcea51605b143fa1695b4ea5c75bddc (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
http://git.savannah.gnu.org/cgit/grep.git/commit/?id=efa477a2c147c60480ae0de323fd8c50aee4df6e


commit efa477a2c147c60480ae0de323fd8c50aee4df6e
Author: Eric Blake <address@hidden>
Date:   Tue Oct 23 11:30:29 2012 +0200

    build: default to --enable-gcc-warnings in a git tree
    
    Anyone building from cloned sources 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 default
    can still be overridden with --disable-gcc-warnings.
    * configure.ac (gl_gcc_warnings): Set default based on environment.

diff --git a/configure.ac b/configure.ac
index a6168c7..1e51ffc 100644
--- a/configure.ac
+++ b/configure.ac
@@ -94,7 +94,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]
 )
 
 if test "$gl_gcc_warnings" = yes; then

-----------------------------------------------------------------------

Summary of changes:
 configure.ac |    6 +++++-
 1 files changed, 5 insertions(+), 1 deletions(-)


hooks/post-receive
-- 
grep