The final linkage of games-emulation/pcsx2-1.7.5312 fails due to unresolved symbols belonging to libQt6Core.so, which is part of dev-qt/qtbase, if dev-qt/qtbase-6.6.1-r4 was compiled using GCC compiler. The issue disappears if qtbase is rebuild using CLANG compiler. Reproducible: Always
Created attachment 884244 [details] build.log
Created attachment 884245 [details] emerge --info
Odd, my qtbase is built with gcc and I do not have that problem. It's also been nearly 3 weeks since pcsx2 started to force clang but this is the first time I hear of issues. I'd assume there's something unusual happening here (maybe related to hardened somehow?). What does `emerge -pvqO clang-common` say?
(In reply to Ionen Wolkens from comment #3) > What does `emerge -pvqO clang-common` say? Oh.. on that note I think I know what's happening. Did you set USE=default-libcxx on clang-common despite this *not* being a libcxx system? This is a system-changing option and shouldn't be casually enabled. This would break any packages using clang and c++ libraries that were linked against libstdc++ rather than libc++.
And uh, please rebuild your qtbase with gcc again because this is going to be a mess if it stays linked with libc++
(In reply to Ionen Wolkens from comment #4) > (In reply to Ionen Wolkens from comment #3) > > What does `emerge -pvqO clang-common` say? > Oh.. on that note I think I know what's happening. > > Did you set USE=default-libcxx on clang-common despite this *not* being a > libcxx system? This is a system-changing option and shouldn't be casually > enabled. This would break any packages using clang and c++ libraries that > were linked against libstdc++ rather than libc++. Thank yo, removing degault-libcxx fixed the issur
