Austin Seipp 5d8bd748f3 chrony: fix build break from libseccomp 2.4.2 ... 03be1adb bumped libseccomp to 2.4.2, which has this note in the changelog: "Stop defining __NR_x values for syscalls that don't exist, libseccomp now uses __SNR_x internally" This change means that invalid syscalls for Linux that aren't defined in glibc will no longer work. In this unlucky case, 'chrony' was trying to reference the syscall number for 'ppoll', which doesn't exist. Fixing this is easy with a simple patch. This also includes another patch from upstream, which allows clock_adjtime in the seccomp filter list. This is a robustness measure for future glibc versions that use clock_adjutime inside adjtimex(). Signed-off-by: Austin Seipp <aseipp@pobox.com>		2019-12-05 18:35:43 -06:00
..
allow-clock_adjtime.patch	chrony: fix build break from libseccomp 2.4.2	2019-12-05 18:35:43 -06:00
default.nix	chrony: fix build break from libseccomp 2.4.2	2019-12-05 18:35:43 -06:00
fix-seccomp-build.patch	chrony: fix build break from libseccomp 2.4.2	2019-12-05 18:35:43 -06:00