qt5-qtwebengine recently started to fail to build on aarch64 after the introduction of glibc-2.28.9000 into rawhide, link to koji build: https://koji.fedoraproject.org/koji/buildinfo?buildID=1168868 Snippet of aarch64 build.log shows: In file included from ../../3rdparty/chromium/sandbox/linux/system_headers/arm64_linux_syscalls.h:8, from ../../3rdparty/chromium/sandbox/linux/system_headers/linux_syscalls.h:33, from ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/syscall_sets.cc:8: ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/syscall_sets.cc: In static member function 'static bool sandbox::SyscallSets::IsFileSystem(int)': ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/syscall_sets.cc:112:10: error: '__NR3264_fstatat' was not declared in this scope case __NR_newfstatat: // fstatat(). EPERM not a valid errno. ^~~~~~~~~~~~~~~ ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/syscall_sets.cc: In static member function 'static bool sandbox::SyscallSets::IsAllowedFileSystemAccessViaFd(int)': ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/syscall_sets.cc:161:10: error: '__NR3264_fstat' was not declared in this scope case __NR_fstat: From a quick perusal, it appears the relevant webengine code snippets are wrapped with #ifarch arm So 2 possibilities I see offhand: * fstat-related macro handling changed on aarch64 * #ifarch arm didn't cover aarch64 before but does now I filed upstream bug at https://bugreports.qt.io/browse/QTBUG-72289
glibc does not provide these __NR_ macros or the arm define. You need to fix that in qt5-qtwebengine (or get the kernel to change the syscall macros).
I think you need this kernel commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8214bdf7d3e69050221aad19ec28826ed6cb4934
borrowed a patch from chromium, https://src.fedoraproject.org/rpms/qt5-qtwebengine/c/522e420ac0706f130f9389ac7943403e334202f4?branch=master