mv -f libWebAssembly.so ../../../lib64/qtcreator/plugins/libWebAssembly.so make[3]: Leaving directory /var/tmp/portage/dev-qt/qt-creator-4.12.0/work/qt-creator-opensource-src-4.12.0/src/plugins/webassembly make[2]: *** No rule to make target cmakeprojectmanager-make_first, needed by sub-mcusupport-make_first. Stop. make[2]: Leaving directory /var/tmp/portage/dev-qt/qt-creator-4.12.0/work/qt-creator-opensource-src-4.12.0/src/plugins make[1]: *** [Makefile:182: sub-plugins-make_first-ordered] Error 2 make[1]: Leaving directory /var/tmp/portage/dev-qt/qt-creator-4.12.0/work/qt-creator-opensource-src-4.12.0/src ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_plasma-libressl-20200428-111526 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-10.1.0 * clang version 10.0.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/10/bin /usr/lib/llvm/10 10.0.0 Available Python interpreters, in order of preference: [1] python3.6 [2] python3.8 [3] python3.7 [4] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) [2] ruby25 (with Rubygems) * Available Rust versions: [1] rust-1.43.0 * [2] rust-bin-1.43.1 The following VMs are available for generation-2: *) IcedTea JDK 3.15.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm The Glorious Glasgow Haskell Compilation System, version 8.0.2 timestamp(s) of HEAD at this tinderbox image: /var/db/repos/gentoo Sun 10 May 2020 07:35:16 PM UTC /var/db/repos/libressl Sat 11 Apr 2020 05:02:25 AM UTC emerge -qpvO dev-qt/qt-creator [ebuild N ] dev-qt/qt-creator-4.12.0 USE="autotest clang designer help lsp qmldesigner webengine -android -baremetal -beautifier -boot2qt -clearcase -cmake -cppcheck -ctfvisualizer -cvs -doc -git -glsl -ios -mercurial -modeling -nim -perforce -perfprofiler -python -qbs -qmlprofiler -qnx -remotelinux -scxml -serialterminal -silversearcher -subversion -systemd -test -valgrind -winrt" L10N="sl -cs -da -de -fr -ja -pl -ru -uk -zh-CN -zh-TW"
Created attachment 638024 [details] emerge-info.txt
Created attachment 638026 [details] dev-qt:qt-creator-4.12.0:20200510-200633.log.bz2
Created attachment 638028 [details] emerge-history.txt
Created attachment 638030 [details] environment
Created attachment 638032 [details] etc.portage.tbz2
Created attachment 638034 [details] temp.tbz2
Bump was done by Jason so I'll CC him here.
Adding msu plugin to USE and REQUIRED_USE fixes the issue. See: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bbdb6e19709589cf079ce945a0dc9205105188bd
Ah, of course foreign bump was not made from qt overlay template. Well spotted.
Fix appears to be already in progress by the linked PR.
Perhaps I should open a new bug but it may be relevant here. I failed to emerge qt-creator-4.12.0 with default USE flags plus 'designer' and 'examples' with the latter as I have learned form the ebuild is obsolete, right? I got the (only) error: make[1]: *** [Makefile:182: sub-plugins-make_first-ordered] Error 2 Then I have analysed the build.log and found NO errors. Got confused. Then I found some forum discussion on how to support cmake in qt-creator and found that the cmake flag should be enabled. Then I found this bug. Seems all unrelated. Then I added 'cmake' to qt-creator USE flags and BINGO! All has emerged like a charm. I do not mind to have the cmake support, so, I'm fine. But the behaviour is not as expected, I guess. Side question: 'examples' USE is effectively replaced by 'doc', right?
zx2c4, is this bug fixed?
(In reply to Andreas Sturmlechner from comment #7) > Bump was done by Jason so I'll CC him here. It was your bump, it is your responsibility to clean up here. Re-assigning.
(In reply to Stefan Strogin from comment #8) > Adding msu plugin to USE and REQUIRED_USE fixes the issue. > > See: > https://gitweb.gentoo.org/repo/gentoo.git/commit/ > ?id=bbdb6e19709589cf079ce945a0dc9205105188bd As Stefan pointed out, I had already "fixed" this bug months ago, before it even appeared in a released version. But of course Jason completely ignored the 9999 ebuild before bumping to 4.12.0...
