Source: libdap Version: 3.15.1-7 Severity: serious Tags: stretch sid User: debian...@lists.debian.org 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): > /bin/bash ./libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. > -I/usr/include/libxml2 -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -W -Wcast-align > -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c -o > libparsers_la-dds.tab.lo `test -f 'dds.tab.cc' || echo './'`dds.tab.cc > libtool: compile: g++ -DHAVE_CONFIG_H -I. -I/usr/include/libxml2 -Wdate-time > -D_FORTIFY_SOURCE=2 -Wall -W -Wcast-align -g -O2 -fstack-protector-strong > -Wformat -Werror=format-security -c dds.tab.cc -fPIC -DPIC -o > .libs/libparsers_la-dds.tab.o > dds.yy: In function 'int ddsparse(libdap::parser_arg*)': > dds.yy:265:15: error: reference to 'array' is ambiguous > part = array; > ^~~~~ > In file included from BaseType.h:55:0, > from Byte.h:44, > from dds.yy:57: > Type.h:50:5: note: candidates are: libdap::Part array > array, > ^~~~~ > In file included from /usr/include/c++/6/tuple:39:0, > from /usr/include/c++/6/bits/stl_map.h:63, > from /usr/include/c++/6/map:61, > from Keywords2.h:30, > from DDS.h:66, > from Vector.h:43, > from Array.h:48, > from dds.yy:66: > /usr/include/c++/6/array:90:12: note: template<class _Tp, > long unsigned int _Nm> struct std::array > struct array > ^~~~~ > make[4]: *** [libparsers_la-dds.tab.lo] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2016/07/13/libdap_3.15.1-7_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.
