Well the answer to the new fails is that we are now "too new" in my
tests I used kernel 5.3 and this is what Focal has. But the final fix
used 5.4-rc levels which brought in all the time64 things.
linux-libc-dev:amd64 5.3.0-21.22
5.3 already has the NR definitions like
/usr/include/x86_64-linux-gnu/bits/syscall.h:182:#ifdef __NR_clock_gettime64
But the updated seccomp code added things like:
src/arch-mips64-syscalls.c
626 +»··{ "clock_settime64", __PNR_clock_settime64 },
Usually there are compat defines inside seccomp include/seccomp.h
But the timers are not there.
So without the timers defined => tests fail re-resolving those
with them defined => build fails missing some other part of the definition.
What we overall need seems instead to be the slightly bigger set of:
44113f30 arch: add support for io-uring related system calls in kernel 5.1
0db8babb api: stop defining __NR_x values for syscalls that don't exist
80177ff2 build: ship seccomp-syscalls.h
be65b26b arch: update the internal syscall tables to Linux v5.4-rc4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849785
Title:
FTBFS on i386/ppc64/s390x (Eoan+Focal)
To manage notifications about this bug go to:
https://bugs.launchpad.net/libseccomp/+bug/1849785/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
