CI: enable compiler warnings

* .travis.yml: here. * README-hacking: We no longer aim at K&R C.
akimd · Sep 8, 2018 · 41c43ef · 41c43ef
1 parent 1dac131
commit 41c43ef
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 6 deletions.
diff --git a/.travis.yml b/.travis.yml
@@ -122,7 +122,7 @@ before_install:
 
 script:
   - ./bootstrap
-  - ./configure CC="$CC" CXX="$CXX"
+  - ./configure --enable-gcc-warnings CC="$CC" CXX="$CXX"
   - make -j2
   - make check VERBOSE=1 TESTSUITEFLAGS=-j2
 
diff --git a/README-hacking b/README-hacking
@@ -273,10 +273,7 @@ release:
 - running "make maintainer-check-release" takes care of running
   maintainer-check, maintainer-check-push and maintainer-check-xml.
 
-- Change tests/atlocal/CFLAGS to add your preferred options.  For instance,
-  "-traditional" to check that the parsers are K&R.  Note that it does not
-  make sense for glr.c, which should be ANSI, but currently is actually GNU
-  C, nor for lalr1.cc.
+- Change tests/atlocal/CFLAGS to add your preferred options.
 
 - Test with a very recent version of GCC for both C and C++.  Testing with
   older versions that are still in use is nice too.
@@ -294,7 +291,7 @@ In particular, be sure to read README-release.
 week before a stable release, to give them time to translate them.  Before
 generating the *.pot files, make sure that po/POTFILES.in and
 runtime-po/POTFILES.in list all files with translatable strings.  This
-helps: grep -l '\<_(' *
+helps: grep -l '\<_(' *.
 
 ** Tests
 See above.