Summary: | Update from =dev-qt/qtgui-5.15.2-r13 to =dev-qt/qtgui-5.15.11-r2 fails to link without qtwayland, but qtwayland is only listed as PDEPENDS | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Andreas Grois <andi> |
Component: | Current packages | Assignee: | Qt Bug Alias <qt> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | andi, ionen, michal.lyszczek |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Andreas Grois
2024-01-14 17:16:21 UTC
For future reference, you can make Portage retain build logs outside of PORTAGE_TMPDIR: https://wiki.gentoo.org/wiki/Portage_log#Always_save_build_logs. qtgui having been unable to build without qtwayland for so long wouldn't really make sense, must be something else going on. And I see no reference to "ColorPicker" in qtwayland's sources, but qtbase does have QPlatformServiceColorPicker defined in its own source (well, not the original one, it's added by *-add-color-picking-support-on-wayland-using-the-XDG-d.patch). Not that I looked too closely at what may be going on here, I cannot reproduce any link failure so far anyhow. (In reply to Ionen Wolkens from comment #2) > Not that I looked too closely at what may be going on here, I cannot > reproduce any link failure so far anyhow. That is, without actually trying to install the ancient qtgui-5.12.2 and update from it. I'd guess it may not have had the patch back then and may be influencing something (or perhaps the patches were different and doing something to qtwayland, haven't looked). fwiw, qtgui-5.15.2-r13 is over 2 years old now and if "upgrading from old" is the cause it's unlikely to be hitting many people. I agree - I wasn't even sure if I should file a report or not. However, I wanted to have the workaround (emerge once without "wayland" use flag) documented somewhere. About the symbols being from qtcore: I noticed that too, and would have expected them to actually be part of one of qtcore's libraries. However, checking which libraries export those symbols using nm confirms that they are only built into qtwayland and qtgui: $ for FILE in /usr/lib64/libQt5*.so ; do echo $FILE; nm -gD $FILE | grep olorPi; done /usr/lib64/libQt5Concurrent.so /usr/lib64/libQt5Core.so /usr/lib64/libQt5DBus.so /usr/lib64/libQt5DesignerComponents.so /usr/lib64/libQt5Designer.so /usr/lib64/libQt5Gui.so 000000000015dee0 T _ZN17QPlatformServices11colorPickerEP7QWindow@@Qt_5_PRIVATE_API 00000000004d79f0 T _ZN27QPlatformServiceColorPicker11colorPickedERK6QColor@@Qt_5_PRIVATE_API 00000000004d7af0 T _ZN27QPlatformServiceColorPicker11qt_metacallEN11QMetaObject4CallEiPPv@@Qt_5_PRIVATE_API 00000000004d7a90 T _ZN27QPlatformServiceColorPicker11qt_metacastEPKc@@Qt_5_PRIVATE_API 00000000005e2120 D _ZN27QPlatformServiceColorPicker16staticMetaObjectE@@Qt_5_PRIVATE_API 00000000004d79d0 T _ZNK27QPlatformServiceColorPicker10metaObjectEv@@Qt_5_PRIVATE_API 00000000005e2088 V _ZTI27QPlatformServiceColorPicker@@Qt_5_PRIVATE_API 0000000000532f70 V _ZTS27QPlatformServiceColorPicker@@Qt_5_PRIVATE_API 00000000005e20a0 V _ZTV27QPlatformServiceColorPicker@@Qt_5_PRIVATE_API /usr/lib64/libQt5Help.so /usr/lib64/libQt5MultimediaGstTools.so /usr/lib64/libQt5Multimedia.so /usr/lib64/libQt5MultimediaWidgets.so /usr/lib64/libQt5Network.so /usr/lib64/libQt5OpenGL.so /usr/lib64/libQt5PrintSupport.so /usr/lib64/libQt5QmlModels.so /usr/lib64/libQt5Qml.so /usr/lib64/libQt5QmlWorkerScript.so /usr/lib64/libQt5QuickControls2.so /usr/lib64/libQt5QuickParticles.so /usr/lib64/libQt5QuickShapes.so /usr/lib64/libQt5Quick.so /usr/lib64/libQt5QuickTemplates2.so /usr/lib64/libQt5QuickTest.so /usr/lib64/libQt5QuickWidgets.so /usr/lib64/libQt5Sql.so /usr/lib64/libQt5Svg.so /usr/lib64/libQt5Test.so /usr/lib64/libQt5WaylandClient.so U _ZN27QPlatformServiceColorPicker11colorPickedERK6QColor@Qt_5_PRIVATE_API U _ZN27QPlatformServiceColorPicker11qt_metacallEN11QMetaObject4CallEiPPv@Qt_5_PRIVATE_API U _ZN27QPlatformServiceColorPicker11qt_metacastEPKc@Qt_5_PRIVATE_API U _ZN27QPlatformServiceColorPicker16staticMetaObjectE@Qt_5_PRIVATE_API U _ZTI27QPlatformServiceColorPicker@Qt_5_PRIVATE_API U _ZTV27QPlatformServiceColorPicker@Qt_5_PRIVATE_API /usr/lib64/libQt5Widgets.so U _ZN27QPlatformServiceColorPicker11colorPickedERK6QColor@Qt_5_PRIVATE_API U _ZN27QPlatformServiceColorPicker16staticMetaObjectE@Qt_5_PRIVATE_API /usr/lib64/libQt5X11Extras.so /usr/lib64/libQt5XcbQpa.so U _ZN27QPlatformServiceColorPicker11colorPickedERK6QColor@Qt_5_PRIVATE_API U _ZN27QPlatformServiceColorPicker11qt_metacallEN11QMetaObject4CallEiPPv@Qt_5_PRIVATE_API U _ZN27QPlatformServiceColorPicker11qt_metacastEPKc@Qt_5_PRIVATE_API U _ZN27QPlatformServiceColorPicker16staticMetaObjectE@Qt_5_PRIVATE_API U _ZTI27QPlatformServiceColorPicker@Qt_5_PRIVATE_API U _ZTV27QPlatformServiceColorPicker@Qt_5_PRIVATE_API /usr/lib64/libQt5Xml.so (this is from my main PC, not the netbook I had the linker issue on) I'm probably blind, but I also can't seem to find the actual definition of these symbols in Qt5... If I could still repro the issue, that might shine some light on it, but given that I can't (what is also utterly puzzling), it's probably best to ignore this bug until someone else manages to repro it. I had the very same problem. I was updating from 5.15.2 as well. But I don't use wayland - only X. Doing emerge -e world helped nothing. For future reference if someone stumbles upon it too. My solution was to just remove all qt `emerge -C 'dev-qt/*'` and run emerge @world again. I also tried to look into qt files, but I did not see any obvious problem. And now I also cannot reproduce this. |