Summary: | dev-qt/qtbase-6.6.0-r1: several test failures because of missing plugins (possibly sparc related?) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Rolf Eike Beer <eike> |
Component: | Current packages | Assignee: | Qt Bug Alias <qt> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | ionen |
Priority: | Normal | Keywords: | PullRequest |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=914033 https://github.com/gentoo/gentoo/pull/39764 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
test log
build.log |
Description
Rolf Eike Beer
![]() Created attachment 874084 [details]
build.log
I get similar errors for qtwayland: qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in "" This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Is this not setting QT_PLUGIN_PATH to the image directory or something like that? There should be no need, this is handled by the build system. fwiw last attempt on sparc did not look as bad (bug #914033), albeit maybe something broke in the plugin loader code here and it's giving misleading errors. I have no idea why this would be happening and never ran into this on amd64 (regardless of if qtbase is already installed or missing). Longshot but maaybe [1] is related? [1] https://bugreports.qt.io/browse/QTBUG-107178 (In reply to Ionen Wolkens from comment #4) > Longshot but maaybe [1] is related? > > [1] https://bugreports.qt.io/browse/QTBUG-107178 (albeit that's supposedly fixed, unless it's making a come back) Not seeing anything else of interest. Maybe try by exporting QT_DEBUG_PLUGINS=1, it'll give paths and everything it tried in the test log. The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=47d10317d785964bf94fb0ebaa3575ca0c6a7b5a commit 47d10317d785964bf94fb0ebaa3575ca0c6a7b5a Author: Ionen Wolkens <ionen@gentoo.org> AuthorDate: 2024-12-17 22:22:17 +0000 Commit: Ionen Wolkens <ionen@gentoo.org> CommitDate: 2024-12-18 04:33:41 +0000 dev-qt/qtbase: unkeyword ~sparc Qt already has a lot of issues on BE arches, and sparc been taking this further with a lot of odd issues that do not seem trivial (we've been skipping some tests only for it too). Been trying to add keywords to Qt6 because Qt5 had them, but realistically not convinced anybody really needed this. There is very few revdeps and USE=qt5 been masked on sparc profiles since 2015 and nobody seems to have complained about that (USE=qt6 been also masked given was missing some keywords still). Will also drop from Qt5 so porting efforts don't hit missing keyword issues. Unlikely that Qt5 fares much better, it merely has tests disabled. This could be revisited if we find actual Qt sparc users. Closes: https://bugs.gentoo.org/916867 Closes: https://bugs.gentoo.org/918896 Closes: https://github.com/gentoo/gentoo/pull/39764 Signed-off-by: Ionen Wolkens <ionen@gentoo.org> dev-qt/qtbase/qtbase-6.7.2-r5.ebuild | 2 +- dev-qt/qtbase/qtbase-6.7.3-r2.ebuild | 2 +- dev-qt/qtbase/qtbase-6.8.1.ebuild | 2 +- dev-qt/qtbase/qtbase-6.8.9999.ebuild | 2 +- dev-qt/qtbase/qtbase-6.9.9999.ebuild | 2 +- dev-qt/qtbase/qtbase-6.9999.ebuild | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) |