I just wanted to do some coding in a KDE application. Therefore I started to set up my development environment using kde-builder.
I followed the instructions defined on the /kde-builder web page.
While compilation of kcoreaddons I get a build aboard.
The error message is:
/usr/include/qt6/QtCore/qglobal.h:13:12: fatal: ‘type_traits’ file not found
When I search for this header file I get these results:
/usr/i686-w64-mingw32/sys-root/mingw/include/c++/type_traits
/usr/i686-w64-mingw32/sys-root/mingw/include/c++/bits/cpp_type_traits.h
/usr/i686-w64-mingw32/sys-root/mingw/include/c++/experimental/type_traits
/usr/i686-w64-mingw32/sys-root/mingw/include/c++/ext/type_traits.h
/usr/i686-w64-mingw32/sys-root/mingw/include/c++/tr1/type_traits
/usr/i686-w64-mingw32/sys-root/mingw/include/c++/tr2/type_traits
/usr/include/c++/14/type_traits
/usr/include/c++/14/bits/cpp_type_traits.h
/usr/include/c++/14/experimental/type_traits
/usr/include/c++/14/ext/type_traits.h
/usr/include/c++/14/tr1/type_traits
/usr/include/c++/14/tr2/type_traits
/usr/include/qt6/QtCore/q20type_traits.h
/usr/include/qt6/QtCore/qxptype_traits.h
/usr/lib64/python3.13/site-packages/pyarrow/src/arrow/python/type_traits.h
/usr/x86_64-w64-mingw32/sys-root/mingw/include/c++/type_traits
/usr/x86_64-w64-mingw32/sys-root/mingw/include/c++/bits/cpp_type_traits.h
/usr/x86_64-w64-mingw32/sys-root/mingw/include/c++/experimental/type_traits
/usr/x86_64-w64-mingw32/sys-root/mingw/include/c++/ext/type_traits.h
/usr/x86_64-w64-mingw32/sys-root/mingw/include/c++/tr1/type_traits
/usr/x86_64-w64-mingw32/sys-root/mingw/include/c++/tr2/type_traits
A temporary solution is to not fulfill the dependency to Shiboken6.
These are the packages that I do not consider:
shiboken6-0:6.8.0-2.fc41.x86_64
python3-pyside6-0:6.8.0-2.fc41.x86_64
python3-shiboken6-0:6.8.0-2.fc41.x86_64
python3-pyside6-devel-0:6.8.0-2.fc41.x86_64
python3-shibokepyside6-tools-0:6.8.0-2.fc41.x86_64
pyside6-tools-0:6.8.0-2.fc41.x86_64
qt.shiboken: (kcoreaddons) Unable to start clang++: Child process set up failed: execve: No such file or directory
/usr/include/qt6/QtCore/qglobal.h:13:12: fatal error: 'type_traits' file not found
(kcoreaddons) Errors in /tmp/bindings_REsoZh.hpp:
/usr/include/qt6/QtCore/qglobal.h:13:12: fatal: 'type_traits' file not found
/tmp/bindings_REsoZh.hpp:1:10: note: in file included from /tmp/bindings_REsoZh.hpp:1:
/home/johnkizer/kde/src/kcoreaddons/python/bindings.h:6:10: note: in file included from /home/johnkizer/kde/src/kcoreaddons/python/bindings.h:6:
/usr/include/qt6/QtCore/QPluginLoader:1:10: note: in file included from /usr/include/qt6/QtCore/QPluginLoader:1:
/usr/include/qt6/QtCore/qpluginloader.h:7:10: note: in file included from /usr/include/qt6/QtCore/qpluginloader.h:7:
...
(kcoreaddons) Clang: 1 diagnostic messages:
/usr/include/qt6/QtCore/qglobal.h:13:12: fatal: 'type_traits' file not found
/tmp/bindings_REsoZh.hpp:1:10: note: in file included from /tmp/bindings_REsoZh.hpp:1:
/home/johnkizer/kde/src/kcoreaddons/python/bindings.h:6:10: note: in file included from /home/johnkizer/kde/src/kcoreaddons/python/bindings.h:6:
/usr/include/qt6/QtCore/QPluginLoader:1:10: note: in file included from /usr/include/qt6/QtCore/QPluginLoader:1:
/usr/include/qt6/QtCore/qpluginloader.h:7:10: note: in file included from /usr/include/qt6/QtCore/qpluginloader.h:7:
...
Keeping temporary file: /tmp/bindings_REsoZh.hpp
shiboken: Error running ApiExtractor.
The most relevant-seeming thing I could find was this Qt bug report, but that says it was fixed in Qt 6.7. If anyone has any ideas, that would be awesome
I’d been struggling with the exact same issue for a week! kde-builder works as expected on VM on a fresh F42, however not in a host.
In my case I was able to make it work installing clang.
Although, this error disappeared, the next one was introduced.
I can’t find logs, but the issue solved by installing a build package for pip3.
I feel like there is something with the path to gcc, though I can’t make it work using env’s or submitting parameters e.g. DCMAKE_CXX_COMPILER:FILEPATH=%{Compiler:Executable:Cxx}
Thank you for bringing this back up! I totally forgot to follow-up here, but I did get some advice in the Matrix chat rooms on this one that included clang, just like you mentioned, and also python3-build - with those, everything in workspace built (except for krdp, but I expected that given the FreeRDP 2 vs 3 difference).