Bug#615157: gcc-4.6: -Wunused-but-set-variable -Werror does not imply -Werror=unused-but-set-variable
Matthias Klose wrote: fyi, here is a partial rebuild with gcc-4.6 without the work around applied: http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20110111-gcc-natty.html A quick grep -F '[-Wunused' finds nothing, while grep -F '[-Werror=unused-but' finds 34 packages: acpidlibaio mutter appmenu-gtk libcrypt-openssl-x509-perl network-manager axis2c liblauncher network-manager-applet bamf libmaa network-manager-pptp btrfs-tools libunique rampart crashlibvoikko trousers desktop-webmail libwps u-boot elfutils likewise-open ubuntuone-client freetype lockfile-progs window-picker-applet ido maximus xen-3 indicator-sessionmdadm jigitmemcached I'll start working from the beginning of the alphabet. Thanks, Matthias. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#615157: gcc-4.6: -Wunused-but-set-variable -Werror does not imply -Werror=unused-but-set-variable
On 27/02/11 at 20:48 -0600, Jonathan Nieder wrote: Matthias Klose wrote: this would require the build logs of all the *sucessful* builds from this rebuild. Indeed, grep -F '[-Wunused-but-set' does not dig up anything. After the rebuild, I did grep for that on all logs, but didn't find anything. I don't have all logs anymore. - Lucas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#615157: gcc-4.6: -Wunused-but-set-variable -Werror does not imply -Werror=unused-but-set-variable
On 28.02.2011 03:48, Jonathan Nieder wrote: Matthias Klose wrote: this would require the build logs of all the *sucessful* builds from this rebuild. Indeed, grep -F '[-Wunused-but-set' does not dig up anything. fyi, here is a partial rebuild with gcc-4.6 without the work around applied: http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20110111-gcc-natty.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#615157: gcc-4.6: -Wunused-but-set-variable -Werror does not imply -Werror=unused-but-set-variable
(-cc: Lucas) Matthias Klose wrote: fyi, here is a partial rebuild with gcc-4.6 without the work around applied: Thanks. For reference, the simplest way I could find to just download the files that matter is wget -r -l 1 -H -Dlaunchpad.net -A gz http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20110111-gcc-natty.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#615157: gcc-4.6: -Wunused-but-set-variable -Werror does not imply -Werror=unused-but-set-variable
(-cc: debian-release) Jonathan Nieder wrote: Matthias Klose wrote: yes, explicitly disabled in the package, for a limited time. If you keep this warning enabled, it will result in too many build failures. Somebody needs to scan the successful build logs of a test rebuild for these warnings, file bug reports, user-tag them with debian-...@lists.debian.org, and after we know what needs to be fixed, we can turn this warning on again. Lucas, would you be interested in this (archive rebuild with gcc-4.6 as gcc)? If so, is there anything I can do to help, aside from looking over the result, writing scripts to categorize failures, and filing bugs if there is consensus after a report on debian-devel? Isn't it already an almost-RC bug (as in, an FTBFS waiting to happen) for packages to use -Werror rather than more targetted options on autobuilders? Sorry, that was unproductive of me. In certain cases (e.g., binutils) it is worth a failed build now and then to get a reliable result. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#615157: gcc-4.6: -Wunused-but-set-variable -Werror does not imply -Werror=unused-but-set-variable
On 27/02/11 at 13:01 -0600, Jonathan Nieder wrote: (-cc: debian-release) Jonathan Nieder wrote: Matthias Klose wrote: yes, explicitly disabled in the package, for a limited time. If you keep this warning enabled, it will result in too many build failures. Somebody needs to scan the successful build logs of a test rebuild for these warnings, file bug reports, user-tag them with debian-...@lists.debian.org, and after we know what needs to be fixed, we can turn this warning on again. Lucas, would you be interested in this (archive rebuild with gcc-4.6 as gcc)? If so, is there anything I can do to help, aside from looking over the result, writing scripts to categorize failures, and filing bugs if there is consensus after a report on debian-devel? Hi, I already did a rebuild, and gave the results to Matthias. You might want to coordinate with him. The results are available at http://people.debian.org/~lucas/logs/2011/02/14/gcc/ L. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#615157: gcc-4.6: -Wunused-but-set-variable -Werror does not imply -Werror=unused-but-set-variable
On 27.02.2011 20:16, Lucas Nussbaum wrote: On 27/02/11 at 13:01 -0600, Jonathan Nieder wrote: (-cc: debian-release) Jonathan Nieder wrote: Matthias Klose wrote: yes, explicitly disabled in the package, for a limited time. If you keep this warning enabled, it will result in too many build failures. Somebody needs to scan the successful build logs of a test rebuild for these warnings, file bug reports, user-tag them with debian-...@lists.debian.org, and after we know what needs to be fixed, we can turn this warning on again. Lucas, would you be interested in this (archive rebuild with gcc-4.6 as gcc)? If so, is there anything I can do to help, aside from looking over the result, writing scripts to categorize failures, and filing bugs if there is consensus after a report on debian-devel? Hi, I already did a rebuild, and gave the results to Matthias. You might want to coordinate with him. The results are available at http://people.debian.org/~lucas/logs/2011/02/14/gcc/ this would require the build logs of all the *sucessful* builds from this rebuild. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#615157: gcc-4.6: -Wunused-but-set-variable -Werror does not imply -Werror=unused-but-set-variable
Matthias Klose wrote: this would require the build logs of all the *sucessful* builds from this rebuild. Indeed, grep -F '[-Wunused-but-set' does not dig up anything. Of 1010 failed packages: * 40 failed with cpp: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found I think cpp is being called by rpcgen in these cases. * 39 had missing headers, based on matching against /\.h: No such file or directory/. This includes things like /usr/include/unistd.h:227:20: fatal error: stddef.h: No such file * 7 had headers that configure considers present but unusable (/present but cannot be compiled/). * ifd-gempc: checking for pcsclite.h... cc -Wall -g -O2 -Wall -fPIC -I. -I../common -DGEMPC=410 -I/usr/include/PCSC -I../Gem cc -Wall -g -O2 -Wall -fPIC -I. -I../common -DGEMPC=410 `pkg-config libpcsclite --cflags` -c -o ../common/GCdeb cc -Wall -g -O2 -Wall -fPIC -I. -I../common -DGEMPC=410 `pkg-config libpcsclite --cflags` -c -o resetGemPC410.o cc -Wall -g -O2 -Wall -fPIC -I. -I../common -DGEMPC=410 -I/usr/include/PCSC -I../GemPC410 -c -o ifdhandler.o no FILE MISSING! * python-prctl: You need to install libc development headers to build this module You need to install libcap development headers to build this module * python-visual: /usr/bin/ld: cannot find -lxcb-render-util * 2 tried to use strings as char * (/error: invalid conversion from 'const char\*'/) * 2 included duplicate typedefs (/redefinition of typedef/). * 5 had configure scripts that question the C preprocessor's sanity (/fails sanity check/). * 5 suffer linking problems I didn't investigate (/undefined reference to/). * 4 c++ libraries are missing symbols (/MISSING:/). * geordi: Couldn't match expected type `Foreign.C.Types.CChar' against inferred type `Word8' * = 598 seem to have had build-dependency installability problems, based on matching logs against /but it is not going to be installed/. Many of these are because the resolver refuses to install gcj, gfortran, etc from experimental unless they are mentioned as explicit versioned build-dependencies. * 129 did not have the right version of the source package available (/Can't find source for/); * 19 provoked a comparison against an uninitialized value (/what(): basic_string::compare/); 14 of those were due to build-depending on the purely virtual libjack0.100.0-dev package. * 12 were /Unable to locate package libopensync0-dev/. * 14 tried to write .gconf files in ~ (/root.*Permission denied/). * gpid tried to write to /usr/src/linux. (/usr/src.*Permission denied/). * 11 were terminated for inactivity (/signal TERM/). * 16 had undeclared identifiers without missing headers (/error:.*undeclared/ or /error:.*not declared/). Some of these might be due to missing #includes or feature test macros. * 2 --- amavisd and hplip --- failed with patch: invalid option -- 'U' * epiphany-browser produced the cryptic dh_girepository: Could not find gir file for Epiphany-2.29.typelib * eucalyptus produced the cryptic taskdef class org.codehaus.groovy.ant.Groovyc cannot be found * archivemail had a debian/rules that does not seem to handle -j well: mv debian/archivemail.1 . mv: cannot stat `debian/archivemail.1': No such file or directory /usr/lib/libgpg-error.a: No such file or directory * gpc4.1 redeclares YYSTYPE. * installation-guide: - updating install-methods.po Floating point exception * kdebindings is too quiet to explain what's wrong. But gcc-4.5 fails it, too. * levee: Looking for cpp (/lib/cpp) (can't run cpp as a pipeline) * libgdal-grass: debian/rules:18: *** GDAL version and GDAL GRASS plugin version are not aligned. Please, upload a proper plugin s * libogre-perl: Ogre.c:40250: error: no matching function for call to 'Ogre::ControllerManager::createGpuProgramTimerParam(Ogre:: /usr/include/OGRE/OgreControllerManager.h:199: note: candidates are: Ogre::Controllerfloat* Ogre::ControllerMan * lua-curl: getconf: Unrecognized variable `LFS_CFLGAS' * meta-kde: 'Breaks' field, reference to 'kdebase-workspace-dev': error in version: version string is empty * monkeysphere: # ssh connection test FAILED. returned: 1, expected: 0 * mseide: build_all.sh: 8: Syntax error: ( unexpected * pbuilder: col: Invalid or incomplete multibyte or wide character * pgtap, postgis, postgresql-pllua: Makefile:49: /usr/lib/postgresql/9.0/lib/pgxs/src/makefiles/pgxs.mk: No such file or directory * php-gettext: PHP Warning: require_once(PHP/CodeCoverage/Filter.php): failed to open stream: No such file or directory in /usr /bin/phpunit on line 38 * plasma-widget-networkmanagement: error: cannot fstat file
Bug#615157: gcc-4.6: -Wunused-but-set-variable -Werror does not imply -Werror=unused-but-set-variable
[removing the builds, not commented here] On 28.02.2011 03:48, Jonathan Nieder wrote: Matthias Klose wrote: this would require the build logs of all the *sucessful* builds from this rebuild. Indeed, grep -F '[-Wunused-but-set' does not dig up anything. Of 1010 failed packages: * 40 failed with cpp: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found I think cpp is being called by rpcgen in these cases. seen to, didn't investigate yet. but maybe recheck first with a newer gcc-4.6 build (as uploaded today). * 39 had missing headers, based on matching against /\.h: No such file or directory/. This includes things like /usr/include/unistd.h:227:20: fatal error: stddef.h: No such file Most of these are ObjC builds. I assume Lucas didn't install gobjc-4.6 (and maybe not gfortran-4.6). * 2 tried to use strings as char * (/error: invalid conversion from 'const char\*'/) is this with -Werror? might be worth adding a FAQ how to fix these. * 5 had configure scripts that question the C preprocessor's sanity (/fails sanity check/). I guess this is the same as the -fuse-linker-plugin error. * 5 suffer linking problems I didn't investigate (/undefined reference to/). ld --no-add-needed * 4 c++ libraries are missing symbols (/MISSING:/). symbols mangling * = 598 seem to have had build-dependency installability problems, based on matching logs against /but it is not going to be installed/. Many of these are because the resolver refuses to install gcj, gfortran, etc from experimental unless they are mentioned as explicit versioned build-dependencies. right, gcj-4.6 not available. * gpc4.1 redeclares YYSTYPE. gone. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#615157: gcc-4.6: -Wunused-but-set-variable -Werror does not imply -Werror=unused-but-set-variable
On 26.02.2011 07:43, Jonathan Nieder wrote: Package: gcc-4.6 Version: 4.6-20110216-1 I would have expected all three to error out. Known problem? yes, explicitly disabled in the package, for a limited time. If you keep this warning enabled, it will result in too many build failures. Somebody needs to scan the successful build logs of a test rebuild for these warnings, file bug reports, user-tag them with debian-...@lists.debian.org, and after we know what needs to be fixed, we can turn this warning on again. Could you work on filing these reports? These reports will end up as release critical bug reports for wheezy, so maybe start filing these with severity important. Matthias -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#615157: gcc-4.6: -Wunused-but-set-variable -Werror does not imply -Werror=unused-but-set-variable
Matthias Klose wrote: yes, explicitly disabled in the package, for a limited time. If you keep this warning enabled, it will result in too many build failures. Somebody needs to scan the successful build logs of a test rebuild for these warnings, file bug reports, user-tag them with debian-...@lists.debian.org, and after we know what needs to be fixed, we can turn this warning on again. Sure, given access to some build logs, I'd be happy to start working through them and filing reports. These reports will end up as release critical bug reports for wheezy, so maybe start filing these with severity important. Isn't it already an almost-RC bug (as in, an FTBFS waiting to happen) for packages to use -Werror rather than more targetted options on autobuilders? Thanks. Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#615157: gcc-4.6: -Wunused-but-set-variable -Werror does not imply -Werror=unused-but-set-variable
Package: gcc-4.6
Version: 4.6-20110216-1
Hi,
Turning on -Werror so the warnings don't scroll by.
$ cat test.c
#include stdio.h
int main(void)
{
int x;
x = printf(hello, world\n);
return 0;
}
$
$ gcc-4.6 -Wall -Werror test.c; echo $?
test.c: In function ‘main’:
test.c:5:6: warning: variable ‘x’ set but not used [-Wunused-but-set-variable]
0
$ gcc-4.6 -Wunused-but-set-variable -Werror test.c; echo $?
test.c: In function ‘main’:
test.c:5:6: warning: variable ‘x’ set but not used [-Wunused-but-set-variable]
0
$ gcc-4.6 -Werror=unused-but-set-variable test.c; echo $?
test.c: In function ‘main’:
test.c:5:6: error: variable ‘x’ set but not used
[-Werror=unused-but-set-variable]
cc1: some warnings being treated as errors
1
I would have expected all three to error out.
Known problem?
Jonathan
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
