FTBFS against g++ 11
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
thin-provisioning-tools (Debian) |
Fix Released
|
Unknown
|
|||
thin-provisioning-tools (Ubuntu) |
Fix Released
|
Undecided
|
Christian Ehrhardt |
Bug Description
thin-provisioni
/usr/src/
450 | args_num, ::testing:
| ^
/usr/src/
120 | std::is_
| ^~~~~~~~~~~
/usr/src/
296 | #define MOCK_METHOD0(m, ...) GMOCK_INTERNAL_
| ^~~~~~~
unit-tests/
42 | MOCK_METHOD0(wait, optional<
| ^~~~~~~~~~~~
Related branches
- Miriam España Acebal (community): Approve
- Canonical Server packageset reviewers: Pending requested
- git-ubuntu import: Pending requested
-
Diff: 50 lines (+13/-1)3 files modifieddebian/changelog (+7/-0)
debian/control (+4/-1)
debian/rules (+2/-0)
Changed in thin-provisioning-tools (Ubuntu): | |
status: | New → Triaged |
Changed in thin-provisioning-tools (Debian): | |
status: | Unknown → New |
tags: | added: server-todo |
Changed in thin-provisioning-tools (Debian): | |
status: | New → Fix Released |
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 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’ })
Fails, but slightly different (also build errors)
./persistent-
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 ...