Hi all, my stable system is completely broken since the last world update a few days ago. I have no idea where this comes from, but I can't compile any Qt program anymore. I saw this working on my local KGeoTag git clone, cf. the attached console output. Moc fails without any output. Same for KPhotoAlbum, and also for non-KDE Qt programs. I did another world update and revdep-rebuild. I then tried to recompile dev-qt/qtcore, as it ships moc -- and building it also fails (cf. the attached build log). What can even cause this?!
Created attachment 793229 [details] KGeoTag build console output
Created attachment 793232 [details] KPhotoAlbum build console output
Created attachment 793235 [details] dev-qt/qtcore build log
Even if I try to compile Qt directly from sources, without any patches, it fails as soon as moc is involved (the moc Qt builds itself during the build process): make[2]: Entering directory '/home/tobias/tmp/1/qtbase-everywhere-src-5.15.5/build/src/corelib' /home/tobias/tmp/1/qtbase-everywhere-src-5.15.5/build/bin/moc -DQT_NO_LINKED_LIST -DQT_NO_JAVA_STYLE_ITERATORS -DQT_NO_USING_NAMESPACE -DQT_NO_FOREACH -DQFLOAT16_INCLUDE_FAST -DELF_INTERPRETER=\"/lib64/ld-linux-x86-64.so.2\" -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_BUILD_CORE_LIB -DQT_BUILDING_QT -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER -DQT_DEPRECATED_WARNINGS -DQT_DISABLE_DEPRECATED_BEFORE=0x050000 -DQT_DEPRECATED_WARNINGS_SINCE=0x060000 -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_NO_DEBUG -DPCRE2_CODE_UNIT_WIDTH=16 --include /home/tobias/tmp/1/qtbase-everywhere-src-5.15.5/build/src/corelib/.moc/moc_predefs.h -I/home/tobias/tmp/1/qtbase-everywhere-src-5.15.5/mkspecs/linux-g++ -I/home/tobias/tmp/1/qtbase-everywhere-src-5.15.5/src/corelib -I/home/tobias/tmp/1/qtbase-everywhere-src-5.15.5/src/3rdparty/zlib/src -I/home/tobias/tmp/1/qtbase-everywhere-src-5.15.5/build/src/corelib/global -I/home/tobias/tmp/1/qtbase-everywhere-src-5.15.5/src/3rdparty/md5 -I/home/tobias/tmp/1/qtbase-everywhere-src-5.15.5/src/3rdparty/md4 -I/home/tobias/tmp/1/qtbase-everywhere-src-5.15.5/src/3rdparty/sha3 -I/home/tobias/tmp/1/qtbase-everywhere-src-5.15.5/src/3rdparty/harfbuzz/src -I/home/tobias/tmp/1/qtbase-everywhere-src-5.15.5/src/3rdparty/forkfd -I/home/tobias/tmp/1/qtbase-everywhere-src-5.15.5/src/3rdparty/tinycbor/src -I/home/tobias/tmp/1/qtbase-everywhere-src-5.15.5/src/corelib/.rcc -I/home/tobias/tmp/1/qtbase-everywhere-src-5.15.5/include -I/home/tobias/tmp/1/qtbase-everywhere-src-5.15.5/include/QtCore -I/home/tobias/tmp/1/qtbase-everywhere-src-5.15.5/build/include -I/home/tobias/tmp/1/qtbase-everywhere-src-5.15.5/build/include/QtCore -I/home/tobias/tmp/1/qtbase-everywhere-src-5.15.5/include/QtCore/5.15.5 -I/home/tobias/tmp/1/qtbase-everywhere-src-5.15.5/include/QtCore/5.15.5/QtCore -I/home/tobias/tmp/1/qtbase-everywhere-src-5.15.5/build/include/QtCore/5.15.5 -I/home/tobias/tmp/1/qtbase-everywhere-src-5.15.5/build/include/QtCore/5.15.5/QtCore -I. -I/usr/lib/gcc/x86_64-pc-linux-gnu/11.3.0/include/g++-v11 -I/usr/lib/gcc/x86_64-pc-linux-gnu/11.3.0/include/g++-v11/x86_64-pc-linux-gnu -I/usr/lib/gcc/x86_64-pc-linux-gnu/11.3.0/include/g++-v11/backward -I/usr/lib/gcc/x86_64-pc-linux-gnu/11.3.0/include -I/usr/lib/gcc/x86_64-pc-linux-gnu/11.3.0/include-fixed -I/usr/include --output-json /home/tobias/tmp/1/qtbase-everywhere-src-5.15.5/src/corelib/animation/qabstractanimation.h -o .moc/moc_qabstractanimation.cpp make[2]: *** [Makefile:10877: .moc/moc_qabstractanimation.cpp] Killed make[2]: Leaving directory '/home/tobias/tmp/1/qtbase-everywhere-src-5.15.5/build/src/corelib' make[1]: *** [Makefile:223: sub-corelib-make_first] Error 2 make[1]: Leaving directory '/home/tobias/tmp/1/qtbase-everywhere-src-5.15.5/build/src' make: *** [Makefile:51: sub-src-make_first] Error 2
Could you share dmesg output? It's being killed by something but I have no idea what.
Now I'm about to lose my faith. I rebooted my machine and the error was gone. I never ever had something like this in my 18 years of gentoo until now. So ... whatever. Sorry for the noise. But I simply don't get this ...
(In reply to Tobias Leupold from comment #6) > Now I'm about to lose my faith. I rebooted my machine and the error was gone. > > I never ever had something like this in my 18 years of gentoo until now. > > So ... whatever. Sorry for the noise. But I simply don't get this ... This sounds a lot like you might have failing memory. I recommend doing a memtest.
I did so, and memtest yielded no errors. Very strange.
