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