Your message dated Wed, 16 Feb 2022 20:27:43 +0100 with message-id <yg1ql7eosflfg...@shell.thinkmo.de> and subject line Re: Processed: Re: Bug#984366: thin-provisioning-tools: ftbfs with GCC-11 has caused the Debian Bug report #1005645, regarding googletest: ftbfs with GCC-11 to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1005645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005645 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: src:thin-provisioning-tools Version: 0.9.0-1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/thin-provisioning-tools_0.9.0-1_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] | ^~~~~~~ In file included from /usr/src/googletest/googlemock/include/gmock/gmock-function-mocker.h:42, from /usr/src/googletest/googlemock/include/gmock/gmock.h:61, from unit-tests/copier_t.cc:19: /usr/src/googletest/googlemock/include/gmock/gmock-spec-builders.h:2021:37: error: expression cannot be used as a function 2021 | nullptr) \ | ^ /usr/src/googletest/googlemock/include/gmock/gmock-spec-builders.h:2028:3: note: in expansion of macro ‘GMOCK_ON_CALL_IMPL_’ 2028 | GMOCK_ON_CALL_IMPL_(obj, InternalExpectedAt, call) | ^~~~~~~~~~~~~~~~~~~ unit-tests/copier_t.cc:220:9: note: in expansion of macro ‘EXPECT_CALL’ 220 | EXPECT_CALL(engine_, wait()). | ^~~~~~~~~~~ unit-tests/copier_t.cc: In member function ‘virtual void CopierTests_wait_can_timeout_Test::TestBody()’: /usr/src/googletest/googlemock/include/gmock/gmock-spec-builders.h:2021:37: error: expression cannot be used as a function 2021 | nullptr) \ | ^ /usr/src/googletest/googlemock/include/gmock/gmock-spec-builders.h:2028:3: note: in expansion of macro ‘GMOCK_ON_CALL_IMPL_’ 2028 | GMOCK_ON_CALL_IMPL_(obj, InternalExpectedAt, call) | ^~~~~~~~~~~~~~~~~~~ unit-tests/copier_t.cc:260:9: note: in expansion of macro ‘EXPECT_CALL’ 260 | EXPECT_CALL(engine_, wait(micro)). | ^~~~~~~~~~~ unit-tests/copier_t.cc:261:33: error: ‘make_wr’ was not declared in this scope 261 | WillOnce(Return(make_wr(true, 0u))); | ^~~~~~~ In file included from /usr/src/googletest/googlemock/include/gmock/gmock-function-mocker.h:42, from /usr/src/googletest/googlemock/include/gmock/gmock.h:61, from unit-tests/copier_t.cc:19: /usr/src/googletest/googlemock/include/gmock/gmock-spec-builders.h:2021:37: error: expression cannot be used as a function 2021 | nullptr) \ | ^ /usr/src/googletest/googlemock/include/gmock/gmock-spec-builders.h:2028:3: note: in expansion of macro ‘GMOCK_ON_CALL_IMPL_’ 2028 | GMOCK_ON_CALL_IMPL_(obj, InternalExpectedAt, call) | ^~~~~~~~~~~~~~~~~~~ unit-tests/copier_t.cc:267:9: note: in expansion of macro ‘EXPECT_CALL’ 267 | EXPECT_CALL(engine_, wait(micro)). | ^~~~~~~~~~~ unit-tests/copier_t.cc:268:61: error: reference to ‘optional’ is ambiguous 268 | WillOnce(DoAll(SetArgReferee<0>(0u), Return(optional<wait_result>()))); | ^~~~~~~~ In file included from /usr/src/googletest/googletest/include/gtest/internal/gtest-port.h:2308, from /usr/src/googletest/googlemock/include/gmock/internal/gmock-port.h:56, from /usr/src/googletest/googlemock/include/gmock/internal/gmock-internal-utils.h:46, from /usr/src/googletest/googlemock/include/gmock/gmock-actions.h:145, from /usr/src/googletest/googlemock/include/gmock/gmock.h:59, from unit-tests/copier_t.cc:19: /usr/include/c++/11/optional:60:11: note: candidates are: ‘template<class _Tp> class std::optional’ 60 | class optional; | ^~~~~~~~ In file included from /usr/include/boost/optional/optional.hpp:58, from /usr/include/boost/optional.hpp:15, from ./block-cache/io_engine.h:7, from ./block-cache/copier.h:4, from unit-tests/copier_t.cc:20: /usr/include/boost/optional/optional_fwd.hpp:23:25: note: ‘template<class T> class boost::optional’ 23 | template<class T> class optional ; | ^~~~~~~~ unit-tests/copier_t.cc:268:81: error: expected primary-expression before ‘>’ token 268 | WillOnce(DoAll(SetArgReferee<0>(0u), Return(optional<wait_result>()))); | ^ unit-tests/copier_t.cc:268:83: error: expected primary-expression before ‘)’ token 268 | WillOnce(DoAll(SetArgReferee<0>(0u), Return(optional<wait_result>()))); | ^ make[2]: *** [unit-tests/Makefile:84: unit-tests/copier_t.gmo] Error 1 make[2]: Leaving directory '/<<PKGBUILDDIR>>' make[1]: *** [debian/rules:20: override_dh_auto_test] Error 2 make[1]: Leaving directory '/<<PKGBUILDDIR>>' make: *** [debian/rules:10: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
--- End Message ---
--- Begin Message ---On Sun, Feb 13, 2022 at 12:01:47PM -0600, Steven Robbins wrote: > Can we get a more recent build attempt log to demonstrate it remains a > problem? It still fails. But the problem is more mundane. It's c++ and the unusable error messages of gcc. In this case the conflict between "boost::optional<int> wait()" and "MOCK_METHOD(std::optional<int>, wait, ())" which was hidden by several "using namespace". Bastian -- We have phasers, I vote we blast 'em! -- Bailey, "The Corbomite Maneuver", stardate 1514.2
--- End Message ---
