Could finally build and run Slicer on Arch (with VTK8).
I had to :
downgrade GCC from 11.0 to previous 10.2, else Python 3.6.7 fails at runtime with assigned tasks (ensurepip, setuptools),
revert qt5-base to the previous one not built by GCC 11.0, else CTKAppLauncher would not link to QtCore.
[ 96%] Linking CXX executable bin/CTKAppLauncher
/usr/bin/ld: /usr/lib/libQt5Core.so.5.15.2: undefined reference to `std::__exception_ptr::exception_ptr::_M_release()@CXXABI_1.3.13'
/usr/bin/ld: /usr/lib/libQt5Widgets.so.5.15.2: undefined reference to `std::__throw_bad_array_new_length()@GLIBCXX_3.4.29'
/usr/bin/ld: /usr/lib/libQt5Core.so.5.15.2: undefined reference to `std::__exception_ptr::exception_ptr::_M_addref()@CXXABI_1.3.13'
I tend to forget that Arch moves on very fast, and hope that built SlicerPython, of whatever version, becomes functional again with latest compilers.
It’s a temporary solution. ArchLinux would keep updating to the latest gcc. Other distribution will also update gcc soon or later.
I also encounter compiling error trigger by gdcm, which is needed in ITK subproject.
see also Porting to GCC 11 - GNU Project - Free Software Foundation (FSF) for gcc 10 → gcc 11 upgrade porting changes.