https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: x11-misc/copyq-5.0.0 fails to compile. Discovered on: amd64 (internal ref: ci) NOTE: This machine uses GCC-11: https://gcc.gnu.org/gcc-11/porting_to.html If you think this is a GCC-11 related issue, please block bug 732706.
CC'ing also the author of the commit (3f99aff1b352066b103f74e1cc284f1a4f1bbc96)
Created attachment 745860 [details] build.log build log and emerge --info
Created attachment 745863 [details] 1-CMakeOutput.log 1-CMakeOutput.log
Possible context of error(s): Could NOT find QtWaylandScanner (missing: QtWaylandScanner_EXECUTABLE)
Did a quick rebuild on my machine (also GCC 11) and couldn't reproduce this error. QtWaylandScanner is provided by the dev-qt/qtwayland dependency, which you do have installed, so that's a little surprising. In my case, the qtwaylandscanner binary resides in /usr/lib64/qt5/bin/. Can you check if it actually exists on your system? Also, in case you ever tried, were you able to compile 4.1.0?
did you try the same use combo? I see -X
Can't try it out right now, but looks like that might be the culprit. Are you using -X on purpose? It should be enabled by default on all desktop profiles.
Created attachment 745920 [details] qtwayland build.log + emerge --info.txt Looks like a qtwayland bug rather than this package. Here's the build.log for my qtwayland.. it didn't install a single file, so of course it's not finding it. This is on a minimal system with a lot of things disabled, including USE=-wayland (In reply to Christian Schroeder from comment #7) > Can't try it out right now, but looks like that might be the culprit. Are > you using -X on purpose? It should be enabled by default on all desktop > profiles. Among other things, tinderboxes are trying to find missing dependencies -- and defaults that can be freely disabled aren't a resolution to that. Not that -X was the issue here.
(In reply to Ionen Wolkens from comment #8) > Not that -X was the issue here. Actually, correction, it /is/ the issue -- or at least on a USE=-wayland system. Not that this changes qtwayland installing nothing isn't right, so I don't think copyq depending on [X] would be right.
(In reply to Ionen Wolkens from comment #8) > Here's the build.log for my qtwayland.. it didn't install a single file, so > of course it's not finding it. But is that actually caused by -X? It seems from the logs that it doesn't build (and install) anything because it can't find Wayland, which is an unconditional dependency of dev-qt/qtwayland and should thus be present... Or is it that qmake doesn't find Wayland even though it's installed?
(In reply to Christian Schroeder from comment #10) > (In reply to Ionen Wolkens from comment #8) > > Here's the build.log for my qtwayland.. it didn't install a single file, so > > of course it's not finding it. > > But is that actually caused by -X? It seems from the logs that it doesn't > build (and install) anything because it can't find Wayland, which is an > unconditional dependency of dev-qt/qtwayland and should thus be present... > Or is it that qmake doesn't find Wayland even though it's installed? With USE=X it does build something, it's likely a combination of having both X disabled on this and wayland disabled other stuff that leads to getting nothing (i.e. a configuration that doesn't really make sense but is currently allowed). Not that I really looked into it much.
(In reply to Ionen Wolkens from comment #11) > > But is that actually caused by -X? It seems from the logs that it doesn't > > build (and install) anything because it can't find Wayland, which is an > > unconditional dependency of dev-qt/qtwayland and should thus be present... > > Or is it that qmake doesn't find Wayland even though it's installed? Oh I see now, it's because qtwayland has no BDEPEND on dev-util/wayland-scanner
(In reply to Ionen Wolkens from comment #12) > Oh I see now, it's because qtwayland has no BDEPEND on > dev-util/wayland-scanner If that fixes it for you, then I think this might be a different issue than what Agostino reported since according to his logs, he did have wayland-scanner installed when he emerged qtwayland (which requires wayland, which in turn has a BDEPEND on wayland-scanner).
(In reply to Christian Schroeder from comment #13) > (In reply to Ionen Wolkens from comment #12) > > Oh I see now, it's because qtwayland has no BDEPEND on > > dev-util/wayland-scanner > If that fixes it for you, then I think this might be a different issue than > what Agostino reported since according to his logs, he did have > wayland-scanner installed when he emerged qtwayland (which requires wayland, > which in turn has a BDEPEND on wayland-scanner). Hrm, you're right. There may be more reasons it can end up installing no files. Kind of bother me that it doesn't simply error out when dependencies are missing. I'll just leave the summary reasons open to discussion.
@ago maybe check if your qtwayland really has no installed files just to be sure this is really what's happening for you as well?
I still cannot reproduce ionen's configure output: > Running configuration tests... > Checking for Wayland client library... no > Checking for Wayland EGL library... no > Checking for wayland-server... no > Done running configuration tests. even without wayland-scanner installed. What I get is: > Running configuration tests... > Checking for Wayland client library... yes > Checking for Wayland cursor library... yes > Checking for wayland-scanner... no > Checking for Wayland EGL library... yes > Checking for wayland-server... yes > Done running configuration tests. That being said, a dep on dev-util/wayland-scanner is definitely missing from qtwayland. It looks like dev-libs/wayland used to provide wayland-scanner, but that was split off into its own package at some point (https://github.com/gentoo/gentoo/pull/18751) (In reply to Ionen Wolkens from comment #14) > Kind of bother me that it doesn't simply error out when dependencies are > missing. I'll just leave the summary reasons open to discussion. Yes that's annoying... and it happens with other Qt5 packages as well.
(In reply to Davide Pesavento from comment #16) > I still cannot reproduce ionen's configure output: Oh my bad, while I /was/ getting empty qtwayland because of wayland-scanner (binpkg wayland, so it was never needed), the log had something more. My test scripts emerges dependencies with native-symlinks, except for the last package (which turned out to be qtwayland when I tried it individually), and I forgot to turn that off which I normally do given I know full well qmake doesn't play well without them. That aside, native-symlinks were enabled in ago's log, so it's not that.
Wait a minute, what's going on here? dev-qt/qtgui-5.15.2-r13:5/5.15.2 -accessibility -dbus -debug egl -eglfs -evdev gif -gles2-only -ibus -jpeg libinput -linuxfb png -test -tslib -tuio udev -vnc -vulkan -wayland -X REQUIRED_USE=" || ( eglfs X ) yet both are unset There was another oddity at bug #819027 Is something up with ago's tinderbox?
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/qt.git/commit/?id=62332410050ad50c0751ab255531c23531096207 commit 62332410050ad50c0751ab255531c23531096207 Author: Davide Pesavento <pesa@gentoo.org> AuthorDate: 2021-10-20 23:48:13 +0000 Commit: Davide Pesavento <pesa@gentoo.org> CommitDate: 2021-10-20 23:48:13 +0000 dev-qt/qtwayland: add missing dep on dev-util/wayland-scanner Bug: https://bugs.gentoo.org/818997 Package-Manager: Portage-3.0.28, Repoman-3.0.3 Signed-off-by: Davide Pesavento <pesa@gentoo.org> dev-qt/qtwayland/qtwayland-5.15.2.9999.ebuild | 3 +++ 1 file changed, 3 insertions(+)
Well, I tried many random combinations of flags (given list doesn't seem to reflect what's used), but couldn't find another situation where I can reproduce this (only with no wayland-scanner, or -native-symlinks). I think need ago's help here, or at least to verify if this qtwayland is really installing no files.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b4766d8df05d3c6fa584a6b81f684cb51568227e commit b4766d8df05d3c6fa584a6b81f684cb51568227e Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2021-10-16 12:52:53 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2021-11-07 23:38:49 +0000 dev-qt/qtwayland: 5.15.2-r15 version bump at KDE 992833ca Add missing dep on dev-util/wayland-scanner. Upstream fixes: "Fix the logic for decoding modifiers map in Wayland text input protocol" QTBUG: https://bugreports.qt.io/browse/QTBUG-97094 "Wayland client: use wl_keyboard to determine active state" https://codereview.qt-project.org/c/qt/qtwayland/+/367306 Pre-requisite of fix in kde-frameworks/kio-5.88.0, see also: https://invent.kde.org/frameworks/kio/-/merge_requests/619 KDE-bug: https://bugs.kde.org/show_bug.cgi?id=421974 "Client: do not empty clipboard when a new popup/window is opened" QTBUG: https://bugreports.qt.io/browse/QTBUG-93474 Thanks-to: Davide Pesavento <pesa@gentoo.org> Bug: https://bugs.gentoo.org/818997 Package-Manager: Portage-3.0.28, Repoman-3.0.3 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> dev-qt/qtwayland/Manifest | 1 + dev-qt/qtwayland/qtwayland-5.15.2-r15.ebuild | 44 ++++++++++++++++++++++++++++ 2 files changed, 45 insertions(+)
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f72c0101bc5af17f71c36ed37ec42ff3d3f272cb commit f72c0101bc5af17f71c36ed37ec42ff3d3f272cb Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2021-12-16 12:20:16 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2021-12-16 12:23:59 +0000 dev-qt/qtwayland: Drop 5.15.2-r14 Closes: https://bugs.gentoo.org/818997 Package-Manager: Portage-3.0.30, Repoman-3.0.3 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> dev-qt/qtwayland/Manifest | 1 - dev-qt/qtwayland/qtwayland-5.15.2-r14.ebuild | 42 ---------------------------- 2 files changed, 43 deletions(-)
