GNU bug report logs - #14817
git source refuse to build with the default --enable-gcc-warnings

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 14817 in the body.
You can then email your comments to 14817 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Charlie Brown <stieizc.33 <at> gmail.com>
To: bug-coreutils <at> gnu.org
Subject: git source refuse to build with the default --enable-gcc-warnings
Date: Mon, 8 Jul 2013 10:43:39 +0800

It seems that a bug in gnulib is stopping coreutils git source from
build with the default --enable-gcc-warnings turned on.
The gnulib team have push a fix in their git source, but I don't know
how to get the gnulib submodule to use the latest git source.
How can I do that switch?
Thanks in advance!


Sincerely,
王文鑫
Charlie


-----------------------------------------------------------------------------------
In file included from lib/fnmatch.c:170:0:
lib/fnmatch_loop.c: In function 'internal_fnmatch':
lib/fnmatch_loop.c:237:21: error: jump skips variable initialization
[-Werror=jump-misses-init]
                     goto normal_bracket;
                     ^
lib/fnmatch_loop.c:601:23: note: label 'normal_bracket' defined here
                       normal_bracket:
                       ^
lib/fnmatch_loop.c:423:26: note: 'is_range' declared here
                     bool is_range = false;
                          ^
lib/fnmatch_loop.c:268:29: error: jump skips variable initialization
[-Werror=jump-misses-init]
                             goto normal_bracket;
                             ^
lib/fnmatch_loop.c:601:23: note: label 'normal_bracket' defined here
                       normal_bracket:
                       ^
lib/fnmatch_loop.c:423:26: note: 'is_range' declared here
                     bool is_range = false;
                          ^
  CC       lib/fseeko.o
In file included from lib/fnmatch.c:266:0:
lib/fnmatch_loop.c: In function 'internal_fnwmatch':
lib/fnmatch_loop.c:237:21: error: jump skips variable initialization
[-Werror=jump-misses-init]
                     goto normal_bracket;
                     ^
lib/fnmatch_loop.c:601:23: note: label 'normal_bracket' defined here
                       normal_bracket:
                       ^
lib/fnmatch_loop.c:423:26: note: 'is_range' declared here
                     bool is_range = false;
                          ^
lib/fnmatch_loop.c:268:29: error: jump skips variable initialization
[-Werror=jump-misses-init]
                             goto normal_bracket;
                             ^
lib/fnmatch_loop.c:601:23: note: label 'normal_bracket' defined here
                       normal_bracket:
                       ^
lib/fnmatch_loop.c:423:26: note: 'is_range' declared here
                     bool is_range = false;
                          ^
cc1: all warnings being treated as errors
make[2]: *** [lib/fnmatch.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory `/mnt/clfs/sources/coreutils'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/mnt/clfs/sources/coreutils'
make: *** [all] Error 2

Message #10 received at 14817-done <at> debbugs.gnu.org (full text, mbox):

From: Pádraig Brady <P <at> draigBrady.com>
To: Charlie Brown <stieizc.33 <at> gmail.com>
Cc: 14817-done <at> debbugs.gnu.org
Subject: Re: bug#14817: git source refuse to build with the default
 --enable-gcc-warnings
Date: Mon, 08 Jul 2013 14:16:08 +0100

On 07/08/2013 03:43 AM, Charlie Brown wrote:
> It seems that a bug in gnulib is stopping coreutils git source from
> build with the default --enable-gcc-warnings turned on.
> The gnulib team have push a fix in their git source, but I don't know
> how to get the gnulib submodule to use the latest git source.
> How can I do that switch?
> Thanks in advance!

Paul already made that change in coreutils:
http://git.sv.gnu.org/gitweb/?p=coreutils.git;a=commit;h=c7dd453

So if you checkout the latest coreutils and then do:
git submodule update

cheers,
Pádraig.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.