I've just added to the list of warnings enabled by gnulib's manywarnings module. This is the sole measure I've had to take in coreutils to avoid the warnings when using the very latest gcc and configuring this package with --enable-gcc-warnings:
>From 9850c74b1f5d15ccfc4061a6d5e58207ee331ffa Mon Sep 17 00:00:00 2001 From: Jim Meyering <meyer...@redhat.com> Date: Sun, 2 Sep 2012 13:42:39 +0200 Subject: [PATCH] maint: accommodate upcoming, expanded list of warnings from gnulib * configure.ac: Disable a new gcc warning, -Wsuggest-attribute=format, since it triggers on copy.c (which I'm not inclined to adjust) and factor.c's use of vfprintf which would appear to require a change to stdio.h. --- configure.ac | 1 + 1 file changed, 1 insertion(+) diff --git a/configure.ac b/configure.ac index 51782a5..627920d 100644 --- a/configure.ac +++ b/configure.ac @@ -128,6 +128,7 @@ if test "$gl_gcc_warnings" = yes; then nw="$nw -Wmissing-format-attribute" # copy.c nw="$nw -Wunsafe-loop-optimizations" # a few src/*.c nw="$nw -Winline" # system.h's readdir_ignoring_dot_and_dotdot + nw="$nw -Wsuggest-attribute=format" # warns about copy.c and factor.c # Using -Wstrict-overflow is a pain, but the alternative is worse. # For an example, see the code that provoked this report: -- 1.7.12.146.g16d26b1
