Created attachment 716781 [details] requested information files Hello, while upgrading kde-plasma vom 5.20.5 to 5.21.5 package libksysguard fails to compile with link errors, so kde is unusable now. /usr/lib/gcc/i686-pc-linux-gnu/8.4.0/../../../../i686-pc-linux-gnu/bin/ld: processcore/CMakeFiles/processcore.dir/cgroup_data_model.cpp.o: in function `KSysGuard::CGroupDataModel::update(KSysGuard::CGroup*) [clone .localalias.191]': cgroup_data_model.cpp:(.text+0x1cee): undefined reference to `std::filesystem::__cxx11::path::_M_split_cmpts()' /usr/lib/gcc/i686-pc-linux-gnu/8.4.0/../../../../i686-pc-linux-gnu/bin/ld: cgroup_data_model.cpp:(.text+0x1cfd): undefined reference to `std::filesystem::__cxx11::directory_iterator::directory_iterator(std::filesystem::__cxx11::path const&, std::filesystem::directory_options, std::error_code*)' /usr/lib/gcc/i686-pc-linux-gnu/8.4.0/../../../../i686-pc-linux-gnu/bin/ld: cgroup_data_model.cpp:(.text+0x1df9): undefined reference to `std::filesystem::__cxx11::directory_iterator::operator*() const' /usr/lib/gcc/i686-pc-linux-gnu/8.4.0/../../../../i686-pc-linux-gnu/bin/ld: cgroup_data_model.cpp:(.text+0x1e28): undefined reference to `std::filesystem::__cxx11::directory_iterator::operator++()' /usr/lib/gcc/i686-pc-linux-gnu/8.4.0/../../../../i686-pc-linux-gnu/bin/ld: cgroup_data_model.cpp:(.text+0x1ef3): undefined reference to `std::filesystem::status(std::filesystem::__cxx11::path const&)' collect2: error: ld returned 1 exit status The build.log and the requested files are placed inside the TAR. CU Tom
/usr/lib/gcc/i686-pc-linux-gnu/8.4.0/<snip> ^^^^^ This is an old gcc, did you perchance forget to revert after using 8.4.0 for cuda? Try to use eselect gcc / gcc-config to use a newer one.
(In reply to Ionen Wolkens from comment #1) > This is an old gcc, did you perchance forget to revert after using 8.4.0 for > cuda? Nevermind that bit, I doubt you're using cuda :) But you do have gcc 10.3 installed, I suggest using it. It'd be good to get the system in a up to date state and do profile migration soon too (if need help with that, support channels would be better than bugzilla).
After switching gcc from v8.4 to v9.3 this package and the remaining upgrades compiled successfully and KDE is running fine so far. THX for the speedy fix. N.B. the system is up to date as it can be, only I'm using an older and working gcc as long as it's possible, avoiding possible hassles with c++ abi changes... ;) CU Tom
(In reply to Tom from comment #3) > After switching gcc from v8.4 to v9.3 this package and the remaining > upgrades compiled successfully and KDE is running fine so far. > > THX for the speedy fix. > > N.B. the system is up to date as it can be, only I'm using an older and > working gcc as long as it's possible, avoiding possible hassles with c++ abi > changes... ;) FWIW, issues on _upgrades_ for GCC are really rare. The last time was *years* ago: https://wiki.gentoo.org/wiki/Upgrading_GCC#ABI_changes_before_gcc-5.1. You'll be able to upgrade GCC with no problems. Just rebuild libtool first to be safe.
Glad it's working, and yes, Gentoo already does a lot of testing to ensure package issues are resolved by the time a new GCC is marked stable. Using gcc11 from ~testing isn't something I can recommended quite yet, but stable gcc10 is just fine and likely to give you less issues (I'm starting to see people hit issues with gcc9 too given it's being less tested than gcc10)
