View previous topic :: View next topic |
Author |
Message |
CaptainBlood Advocate
Joined: 24 Jan 2010 Posts: 3638
|
Posted: Sun May 07, 2023 5:08 pm Post subject: kde-plasma/kwin + gcc:13 and lto ... |
|
|
Seems like LTO requires the whole required dev-qt/* dependencies to be rebuild from gcc:12 to gcc:13:
Code: | Sun May 7 19:44:45 2023 >>> dev-qt/designer-5.15.9
Sun May 7 20:34:18 2023 >>> dev-qt/qtgui-5.15.9
Sun May 7 20:36:38 2023 >>> dev-qt/qtquickcontrols-5.15.9
Sun May 7 20:43:21 2023 >>> dev-qt/qtquickcontrols2-5.15.9
Sun May 7 20:52:08 2023 >>> dev-qt/qtcore-5.15.9
Sun May 7 20:53:44 2023 >>> dev-qt/qttest-5.15.9
Sun May 7 20:54:59 2023 >>> dev-qt/qtconcurrent-5.15.9
Sun May 7 21:02:51 2023 >>> dev-qt/qtwidgets-5.15.9
Sun May 7 21:24:05 2023 >>> dev-qt/qtdeclarative-5.15.9
Sun May 7 21:25:57 2023 >>> dev-qt/qtdbus-5.15.9
Sun May 7 21:31:26 2023 >>> dev-qt/qtwayland-5.15.9
Sun May 7 21:31:42 2023 >>> dev-qt/qtx11extras-5.15.9 | here.
Thks 4 ur attention, interest & support. _________________ USE="-* ..." in /etc/portage/make.conf here, i.e. a countermeasure to portage implicit braces, belt & diaper paradigm
LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. " |
|
Back to top |
|
|
Hu Administrator
Joined: 06 Mar 2007 Posts: 21722
|
Posted: Sun May 07, 2023 5:12 pm Post subject: |
|
|
Why do you think that these rebuilds are required? Nothing in your post shows any errors or warnings, so it is not possible for us to evaluate whether LTO is relevant here. |
|
Back to top |
|
|
CaptainBlood Advocate
Joined: 24 Jan 2010 Posts: 3638
|
Posted: Sun May 07, 2023 6:34 pm Post subject: |
|
|
For the sake of trust Code: | FAILED: bin/kcm_kwin4_genericscripted.so
: && /usr/bin/x86_64-pc-linux-gnu-g++ -fPIC -march=native -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects -pipe -Wa,-mbranches-within-32B-boundaries -fno-operator-names -fno-exceptions -Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type -Werror=init-self -Wvla -Wdate-time -Wsuggest-override -Wlogical-op -fdiagnostics-color=always -Wl,--no-undefined -Wl,--enable-new-dtags -Wl,-O1 -Wl,-fuse-ld=bfd -pthread -shared -o bin/kcm_kwin4_genericscripted.so src/scripting/CMakeFiles/kcm_kwin4_genericscripted.dir/kcm_kwin4_genericscripted_autogen/mocs_compilation.cpp.o src/scripting/CMakeFiles/kcm_kwin4_genericscripted.dir/genericscriptedconfig.cpp.o src/scripting/CMakeFiles/kcm_kwin4_genericscripted.dir/kwineffects_interface.cpp.o -Wl,-rpath,/var/tmp/portage/kde-plasma/kwin-5.27.4.1-r1/work/kwin-5.27.4.1_build/bin: /usr/lib64/libKF5ConfigWidgets.so.5.104.0 /usr/lib64/libKF5Service.so.5.104.0 bin/libkwineffects.so.5.27.4 /usr/lib64/libKF5WidgetsAddons.so.5.104.0 /usr/lib64/libKF5ConfigGui.so.5.104.0 /usr/lib64/libKF5Codecs.so.5.104.0 /usr/lib64/libKF5Auth.so.5.104.0 /usr/lib64/libKF5AuthCore.so.5.104.0 /usr/lib64/libQt5Xml.so.5.15.9 /usr/lib64/libQt5UiTools.a /usr/lib64/libQt5Widgets.so.5.15.9 /usr/lib64//libQt5Widgets.so /usr/lib64//libQt5Gui.so /usr/lib64//libQt5Core.so /usr/lib64//libQt5Widgets.so /usr/lib64//libQt5Gui.so /usr/lib64//libQt5Core.so /usr/lib64/libGL.so /usr/lib64/libKF5I18n.so.5.104.0 /usr/lib64/libKF5ConfigCore.so.5.104.0 /usr/lib64/libQt5DBus.so.5.15.9 /usr/lib64/libKF5CoreAddons.so.5.104.0 /usr/lib64/libKF5WindowSystem.so.5.104.0 /usr/lib64/libX11.so /usr/lib64/libQt5Gui.so.5.15.9 /usr/lib64/libQt5Core.so.5.15.9 /usr/lib64/libxcb.so -Wl,-rpath-link,/var/tmp/portage/kde-plasma/kwin-5.27.4.1-r1/work/kwin-5.27.4.1_build/bin && :
lto1: fatal error: bytecode stream in file '/usr/lib64/libQt5UiTools.a' generated with LTO version 12.0 instead of the expected 13.0
compilation terminated.
lto-wrapper: fatal error: /usr/bin/x86_64-pc-linux-gnu-g++ returned 1 exit status | Thks 4 ur attention, interest & support. _________________ USE="-* ..." in /etc/portage/make.conf here, i.e. a countermeasure to portage implicit braces, belt & diaper paradigm
LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. " |
|
Back to top |
|
|
Hu Administrator
Joined: 06 Mar 2007 Posts: 21722
|
Posted: Sun May 07, 2023 6:48 pm Post subject: |
|
|
That is helpful. It shows this is a problem if you use static libraries that have LTO bytecode in them. That is a generic problem any time you switch compilers while using static libraries with LTO bytecode, and is not specific to Qt. The question then becomes, why is this library static when the others are shared? |
|
Back to top |
|
|
SigHunter n00b
Joined: 24 Mar 2010 Posts: 41 Location: Nürnberg, Germany
|
Posted: Thu May 11, 2023 8:47 pm Post subject: |
|
|
same for me, thanks for listing them all. fixed one, stopped at the next error
unfortunately lto-rebuild does not list or recompile them, aswell as emerge @preserved-rebuild or anything else I tried
no idea about the static/dynamic thing, though |
|
Back to top |
|
|
CaptainBlood Advocate
Joined: 24 Jan 2010 Posts: 3638
|
Posted: Sun May 14, 2023 8:11 am Post subject: |
|
|
No here
However any reason why not to: Code: |
emerge -1 dev-qt/qtgui dev-qt/qtquickcontrols dev-qt/qtquickcontrols2, etc...
emerge -1 kde-plasma/kwin | ?
Thks 4 ur attention, interest & support. _________________ USE="-* ..." in /etc/portage/make.conf here, i.e. a countermeasure to portage implicit braces, belt & diaper paradigm
LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. " |
|
Back to top |
|
|
Hu Administrator
Joined: 06 Mar 2007 Posts: 21722
|
Posted: Sun May 14, 2023 3:18 pm Post subject: |
|
|
That could work, but it might be more efficient to build a list of all static archives that contain obsolete bytecode, then use emerge to rebuild exactly the packages that own them. Can file tell you which version of LTO bytecode is in a static archive? |
|
Back to top |
|
|
|