On Tue, Sep 5, 2023 at 2:21 PM Miroslav Lichvar <mlich...@redhat.com> wrote: > > What libseccomp version do you have? I think such old syscalls should > be handled there. >
Hmm interesting. While the libseccomp version of the system that I tested this on is indeed quite outdated (thanks for the note!), checking the source code seems to show that these syscalls are already handled anyway: https://github.com/seccomp/libseccomp/blob/v2.3.1/include/seccomp.h.in Not sure what is causing the build to fail without this patch. In any case, I will just advocate updating to the latest libseccomp version (and the latest chrony version as well for good measure). I hope that such an update would automagically fix this issue. Thank you! Best regards, James Raphael Tiovalen -- To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.
