Bunch of CMake errors building with qtgui installed Reproducible: Always Steps to Reproduce: 1. emerge =dev-qt/qtgui-5.14.0 2. emerge =kde-frameworks/kwidgetsaddons-5.65.0 (probably forced rebuild)
Created attachment 600064 [details] emerge log
CMake Error at /usr/lib64/cmake/Qt5Gui/Qt5Gui_QICNSPlugin.cmake:4 (_populate_Gui_plugin_properties): _populate_Gui_plugin_properties Macro invoked with incorrect arguments for macro named: _populate_Gui_plugin_properties Call Stack (most recent call first): /usr/lib64/cmake/Qt5Gui/Qt5GuiConfig.cmake:213 (include) /usr/lib64/cmake/Qt5Widgets/Qt5WidgetsConfig.cmake:112 (find_package) /usr/lib64/cmake/Qt5/Qt5Config.cmake:28 (find_package) CMakeLists.txt:18 (find_package) ^ Please make sure your Qt versions are consistent.
(In reply to Andreas Sturmlechner from comment #2) > CMake Error at /usr/lib64/cmake/Qt5Gui/Qt5Gui_QICNSPlugin.cmake:4 > (_populate_Gui_plugin_properties): > _populate_Gui_plugin_properties Macro invoked with incorrect arguments for > macro named: _populate_Gui_plugin_properties > Call Stack (most recent call first): > /usr/lib64/cmake/Qt5Gui/Qt5GuiConfig.cmake:213 (include) > /usr/lib64/cmake/Qt5Widgets/Qt5WidgetsConfig.cmake:112 (find_package) > /usr/lib64/cmake/Qt5/Qt5Config.cmake:28 (find_package) > CMakeLists.txt:18 (find_package) > > > ^ Please make sure your Qt versions are consistent. How do I do this? I type emerge -uDN @world and it fails while forced rebuilding? Is forced rebuilding broken? This is NOT resolved.
Please describe what you mean by 'forced rebuilding'.
$ equery l dev-qt/*
(In reply to Andreas Sturmlechner from comment #5) > $ equery l dev-qt/* I have 5.14 masked now so I can get my system in a working state, so that commands useless, I'll have to report back after I update the rest of my system.
(In reply to Andreas Sturmlechner from comment #4) > Please describe what you mean by 'forced rebuilding'. I mean when portage decides that a package needs to be rebuilt. emerge says "The following packages are causing rebuilds:" when it happens. Whatever that's called.
(In reply to Michael Cook from comment #6) > (In reply to Andreas Sturmlechner from comment #5) > > $ equery l dev-qt/* > > I have 5.14 masked now so I can get my system in a working state, so that > commands useless, I'll have to report back after I update the rest of my > system. Then please re-open when you have more information. There was another report quite like yours today and it simply was an inconsistent Qt installation. In that case I can do nothing for you as I have built kde-frameworks/* countless times against various different Qt 5.14 beta/rc/release versions without issues.
If this is "working" my only guess is having --jobs=12 (really any number here I guess) in my EMERGE_DEFAULT_OPTS is breaking it. But once it fails, I get in a very bad state and portage can't really do ANYTHING until I mask 5.14.
(In reply to Andreas Sturmlechner from comment #8) > (In reply to Michael Cook from comment #6) > > (In reply to Andreas Sturmlechner from comment #5) > > > $ equery l dev-qt/* > > > > I have 5.14 masked now so I can get my system in a working state, so that > > commands useless, I'll have to report back after I update the rest of my > > system. > > Then please re-open when you have more information. There was another report > quite like yours today and it simply was an inconsistent Qt installation. In > that case I can do nothing for you as I have built kde-frameworks/* > countless times against various different Qt 5.14 beta/rc/release versions > without issues. Sounds to me like there is missing dependencies on most likely multiple qt/kde packages that is allowing --jobs > 1 to build stuff before they should.
There is no missing dependency from kde-frameworks/* here. (In reply to Michael Cook from comment #9) > But once it fails, I get in a very bad state and portage can't really do > ANYTHING until I mask 5.14. You should always be able to continue using `emerge -1vu $(qlist -CI dev-qt/*)`.
*** This bug has been marked as a duplicate of bug 703306 ***
(In reply to Andreas Sturmlechner from comment #11) > There is no missing dependency from kde-frameworks/* here. > > (In reply to Michael Cook from comment #9) > > But once it fails, I get in a very bad state and portage can't really do > > ANYTHING until I mask 5.14. > You should always be able to continue using `emerge -1vu $(qlist -CI > dev-qt/*)`. So it's a portage bug then?
emerge -1avu $(qlist -CI dev-qt/*) solved this issue for me. Thanks.
For anyone who comes across this bug looking for answers, this command finally unwedged Qt for me. emerge -av1 $(qlist -IC dev-qt) --ignore-built-slot-operator-deps=y After that, update @world as normal. Other suggestions in this thread did not work for me. Thanks to josef64 on #gentoo for this tip.
