Source: nfstrace Version: 0.4.1-1 Severity: serious Tags: stretch sid User: [email protected] Usertags: qa-ftbfs-20160713 qa-ftbfs Justification: FTBFS with GCC 6 on amd64
Hi, During a rebuild of all packages in sid using the gcc-defaults package available in experimental to make GCC default to version 6, your package failed to build on amd64. For more information about GCC 6 and Stretch, see: - https://wiki.debian.org/GCC6 - https://lists.debian.org/debian-devel-announce/2016/06/msg00007.html Relevant part (hopefully): > /usr/bin/c++ -I/«PKGBUILDDIR»/src -g -O2 -fstack-protector-strong > -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 > -pedantic -Wall -Werror -Wextra -fPIC -fvisibility=hidden -o > CMakeFiles/nfstrace.dir/src/analysis/analysis_manager.cpp.o -c > /«PKGBUILDDIR»/src/analysis/analysis_manager.cpp > In file included from /«PKGBUILDDIR»/src/analysis/nfs_parser.h:28:0, > from /«PKGBUILDDIR»/src/analysis/parsers.h:27, > from /«PKGBUILDDIR»/src/analysis/analysis_manager.h:32, > from /«PKGBUILDDIR»/src/analysis/analysis_manager.cpp:22: > /«PKGBUILDDIR»/src/protocols/nfs/nfs_procedure.h: In destructor > 'NST::protocols::NFSProcedure<ArgType, ResType>::~NFSProcedure()': > /«PKGBUILDDIR»/src/protocols/nfs/nfs_procedure.h:111:9: error: this 'if' > clause does not guard... [-Werror=misleading-indentation] > if(pres) xdr_free((xdrproc_t)proc_t_of(res), (char*)&res ); > ^~ > /«PKGBUILDDIR»/src/protocols/nfs/nfs_procedure.h:112:18: note: ...this > statement, but the latter is misleadingly indented as if it is guarded by the > 'if' > xdr_free((xdrproc_t)xdr_replymsg, (char*)&reply); > ^~~~~~~~ > cc1plus: all warnings being treated as errors > make[3]: *** [CMakeFiles/nfstrace.dir/src/analysis/analysis_manager.cpp.o] > Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2016/07/13/nfstrace_0.4.1-1_unstable_gcc6.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
