Note: it became a PIE executable in Eoan, but haven't we had pie as default much longer?
The difference is in: rc = seccomp_rule_add(ctx, SCMP_ACT_ALLOW, SCMP_SYS(semtimedop), 0); In the bad case it returns -14 Good: Breakpoint 2, seccomp_rule_add (ctx=0x2aa00049260, action=2147418112, syscall=-204, arg_cnt=0) at api.c:429 Bad: Breakpoint 2, seccomp_rule_add (ctx=0x2aa000492a0, action=2147418112, syscall=392, arg_cnt=0) at api.c:429 Look at the syscall number it is very different. In the good case all are -2xx (also all following ones) So maybe "SCMP_SYS(semtimedop)" for s390x no more works well? -- 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/ubuntu/+source/libseccomp/+bug/1849785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
