I was able to reproduce it in sbuild locally.
But reproducing it from upstream git did not work well.
Neither with libgmock-dev from the package
$ ./configure --enable-testing
$ make
$ apt install libgmock-dev
# that is version 1.11.0-3
$ make unit-test
Nor using upstreams get-mock as outlined in their readme
$ apt remove libgmock-dev
$ ./get-gmock.sh
# that fetches head which is at 97a46757 (1.11 plus a few fixes)
$ make clean
$ make
$ make unit-test
Both tests fail, but they do so at different places than the package build
Fails, but slightly different (also build errors)
./persistent-data/data-structures/btree.tcc:698:35: error: no match for
‘operator!=’ (operand types are ‘const value_type’ {aka ‘const
{anonymous}::thing’} and ‘{anonymous}::thing_traits::value_type’ {aka
‘{anonymous}::thing’})
698 | if (value != old_value) {
Furthermore whatever the problem is with upstream, this one does not go away
when installing and forcing gcc-10
Therefore - as-is - I can't report that upstream in a useful way.
Our issue is somewhat special to Debian/Ubuntu builds.
Looking at our delta to upstream ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950028
Title:
FTBFS against g++ 11
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thin-provisioning-tools/+bug/1950028/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
