Closed sunweaver closed 2 years ago
This happens when building maliit-framework 2.3.0(-1) that I am currently preparing for upload to Debian unstable.
There is no maliit-framework 2.3.0. Has experimental/unstable changed to gcc12 default now? I think it might default to c++20 or something, which breaks QtTest?
I am preparing maliit-framework 2.3.0-1 upload to Debian unstable here: https://salsa.debian.org/debian/maliit-framework/-/commit/c13d226f952ec9ebcd30cb75cbe0c16ef96c9065
And yes, unstable has gcc-12 now.
Oh wait, sorry. I just released maliit-keyboard 2.3.1 which is only the keyboard, no framework release. If you force c++17 standard in the compile, does it work?
Nope, c++17 standard does not help. Note that the FTBFS occurs when building the unit test file tests/ut_minputmethodquickplugin/ut_minputmethodquickplugin.cpp
Hrmm, I see there is a new version of libqt5test5
in experimental. I do not see these errors on testing (which has same libqt5test5
as unstable currently), with gcc 11. So either gcc 12 broke something here, or Qt 5.15.5 did. I'm not sure which exactly.
I just tried a build against experiemental (with more recent libqt5test5): this fails. I also tried a build against Debian testing: this succeeds, I can confirm this.
OK, now that gcc-12 made it to testing and I can more easily see the issue myself, I've made a PR to fix this.