https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: dev-libs/plasma-wayland-protocols-1.15.0 fails to compile. Discovered on: amd64 (internal ref: ci) Info about the issue: https://wiki.gentoo.org/wiki/Project:Tinderbox/Common_Issues_Helper#CF0014
Created attachment 914281 [details] build.log build log and emerge --info
So I'm getting a very interesting result here, with plasma-wayland-protocols-9999 from the kde overlay: With kde::e73f617097bdf8e94cb98afecfaacf0636c41cee (the overlay parallel to gentoo::dfb724c40bc747239a13bb847a834d060e0cbc4b ) merged, pwp breaks with apparently the same error -- can't find qt5. But with it reverted -- that is, with ecm_src_configure() defined instead of plain src_configure() -- at least the -9999 live version merges just fine. But if I'm not mistaken, because ecm.eclass isn't inherited the ecm_src_configure definition isn't even used, which I guess means the standard default_src_configure is used -- and for the -9999 live version at least, it's merging and presumably working just fine without the ebuild defining its own src_configure. OK, so the next logical test given that my above result was with -9999 live from the kde overlay and this bug is filed against 1.15.0 in the gentoo tree, is for me to test 1.15.0. A quick ebuild ... configure later, and I've confirmed it fails with the same error when calling the ebuild's src_configure. After a clean, an ebuild file edit to rename the ebuild's src_configure, and another ebuild ... configure... that works! So I get the same results with gentoo:1.15.0 and kde:9999 -- if the ebuild's src_configure runs it screws things up for me while if it's renamed (to ecm_src_configure) so it doesn't trigger, the configure completes just fine -- unlike the tinderbox based on bug 946574 . Not really sure how that result makes sense but that's what I'm getting. Meanwhile, the last time I successfully merged plasma-wayland-protocols, apparently also with the unused ecm_src_configure, was after upstream c26caed537713fd11ddf5cdeaddce66a3b994e0e which was committed Dec 10, as that's the commit I was at previously. When pwp failed to build @ upstream head I immediately tried rebuilding that commit and it failed too, thus demonstrating it wasn't an upstream issue, and I thought I remembered something about pwp in the kde overlay git logs... sure enough. So now the questions are: 1) What's allowing me to configure both kde::9999 and gentoo::1.15.0 with the default src_configure (when the one defined in the ebuild is renamed to not trigger) that's tripping up the tinderbox? 2) What's screwing me up -- and not fixing tinderbox either -- when the one in the ebuild triggers as intended? Hypothesis: Maybe extra-cmake-modules (the upstream package not the ecm eclass) is making the difference? I'm running -9999 of it too of course, while the tinderbox is reporting kde-frameworks/extra-cmake-modules-6.9.0 . (Meson and cmake appear to be the same version mine against tinderbox.)
(In reply to Duncan from comment #2) > Hypothesis: Maybe extra-cmake-modules (the upstream package not the ecm > eclass) is making the difference? I'm running -9999 of it too of course, > while the tinderbox is reporting kde-frameworks/extra-cmake-modules-6.9.0 . > (Meson and cmake appear to be the same version mine against tinderbox.) No. Downgrading to extra-cmake-modules-6.9.0 didn't change my results. So that doesn't appear to be it. BUT... Directly comparing the successful and unsuccessful configures yields something that looks useful: Bad (with the ebuild's src_configure() ): -- Detecting CXX compile features -- Detecting CXX compile features - done -- -- No Qt5 qmake executable found. Can't check QT_INSTALL_PREFIX CMake Error at /usr/share/ECM/modules/ECMQueryQt.cmake:82 (message): No Qt5 qmake executable found. Can't check QT_INSTALL_PLUGINS as required Call Stack (most recent call first): /usr/share/ECM/kde-modules/KDEInstallDirs5.cmake:256 (ecm_query_qt) /usr/share/ECM/kde-modules/KDEInstallDirs.cmake:15 (include) CMakeLists.txt:17 (include) Good (with the ebuild containing an untriggered ecm_src_configure() ): -- Detecting CXX compile features -- Detecting CXX compile features - done -- -- No Qt5 qmake executable found. Can't check QT_INSTALL_PREFIX Installing in /usr. Run /tmp/portage/dev-libs/plasma-wayland-protocols-1.15.0/work/plasma-wayland-protocols-1.15.0_build/prefix.sh to set theenvironment for PlasmaWaylandProtocols. ** Note that it can't find the Qt5 qmake executable in *both* cases. But in the good case it falls back to a default /usr while in the bad case it's fatal. Does specifically setting -DKDE_INSTALL_USE_QT_SYS_PATHS=ON make that fatal? One way to find out! That's it! With the ebuild's src_configure active but the above -DKDE_INSTALL_USE_QT_SYS_PATHS=ON line commented, I get the same fallback result. Why the tinderbox didn't get the fallback as well, thus triggering the original bug 946574 when the test became fatal, while I got the fallback and was able to continue building successfully without the ebuild's src_configure, I don't know. Presumably it's something else that's installed here since the tinderbox will have less installed. So it's that line that's making/breaking it for me. Hopefully that helps you pin down what's going on to fix it for tinderbox, and define away the automagic if need be, for me.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/proj/kde.git/commit/?id=a2ec2eb2b24170498af2907437a97de04ddf1993 commit a2ec2eb2b24170498af2907437a97de04ddf1993 Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2024-12-18 21:18:55 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2024-12-18 21:19:28 +0000 dev-libs/plasma-wayland-protocols: Set QT_MAJOR_VERSION=6 Closes: https://bugs.gentoo.org/946612 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> .../plasma-wayland-protocols/plasma-wayland-protocols-9999.ebuild | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-)
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2a7973632268fbc42b3825decc799b67f890e5fe commit 2a7973632268fbc42b3825decc799b67f890e5fe Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2024-12-18 21:18:55 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2024-12-18 21:21:32 +0000 dev-libs/plasma-wayland-protocols: Set QT_MAJOR_VERSION=6 Closes: https://bugs.gentoo.org/946612 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> .../plasma-wayland-protocols-1.14.0.ebuild | 8 +++----- .../plasma-wayland-protocols-1.15.0.ebuild | 8 +++----- 2 files changed, 6 insertions(+), 10 deletions(-)
