diff options
| author | Paul Eggert <eggert@cs.ucla.edu> | 2016-04-05 07:51:28 -0700 |
|---|---|---|
| committer | Paul Eggert <eggert@cs.ucla.edu> | 2016-04-05 08:09:43 -0700 |
| commit | 5baecbc0ebc11178edd73431b644a5de0a31be25 (patch) | |
| tree | 1b11fc90b0935fa57768d314b4fab457f0c3694a /INSTALL | |
| parent | 93d54ba104bf85d487eb8e90a4857789e0c9a210 (diff) | |
| download | emacs-5baecbc0ebc11178edd73431b644a5de0a31be25.tar.gz | |
Enable GCC warnings in developer builds
However, do not fail; just issue the warnings. Add an option
--enable-gcc-warnings=warn-only to configure, to implement this.
* INSTALL, etc/NEWS: Document this.
* configure.ac (gl_GCC_VERSION_IFELSE): New macro, from coreutils.
(gl_gcc_warnings, WERROR_CFLAGS): Use it to add new option.
Don’t treat --with-x-toolkit=no as a special case when configuring
warnings.
Diffstat (limited to 'INSTALL')
| -rw-r--r-- | INSTALL | 8 |
1 files changed, 5 insertions, 3 deletions
@@ -318,9 +318,11 @@ Use --enable-gcc-warnings to enable compile-time checks that warn about possibly-questionable C code. This is intended for developers and is useful with GNU-compatible compilers. On a recent GNU system there should be no warnings; on older and on non-GNU systems the -generated warnings may still be useful, though you may prefer building -with 'make WERROR_CFLAGS=' so that the warnings are not treated as -errors. +generated warnings may still be useful, though you may prefer +configuring with --enable-gcc-warnings=warn-only so they are not +treated as errors. The default is --enable-gcc-warnings=warn-only if +it appears to be a developer build, and is --disable-gcc-warnings +otherwise. Use --disable-silent-rules to cause 'make' to give more details about the commands it executes. This can be helpful when debugging a build |