[GH-ISSUE #1622] Lists in syscall.c don’t get defined in some cases, compilation error #1089

New issue

Closed

opened 2026-05-05 07:26:16 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-05-05 07:26:16 -06:00

Owner

Originally created by @newbluemoon on GitHub (Oct 28, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1622

In src/fseccomp/syscall.c the list item of the struct SyscallGroupList for @obsolete and @raw-io doesn’t get assigned a value when cross compiling for aarch64. The list gets filled via some #ifdef constructs which don’t seem to be defined so that the result is ... .list = } which leads to a compilation error even when --disable-seccomp is used.

Can the code be modified to assign an empty list if all #ifdefs are undefined and/or not compile the code in the first place when --disable-seccomp is used?

Edit: Sorry, I only searched in open issues, just found closed #1504.

Originally created by @newbluemoon on GitHub (Oct 28, 2017). Original GitHub issue: https://github.com/netblue30/firejail/issues/1622 In `src/fseccomp/syscall.c` the `list` item of the struct `SyscallGroupList` for `@obsolete` and `@raw-io` doesn’t get assigned a value when cross compiling for aarch64. The list gets filled via some `#ifdef` constructs which don’t seem to be defined so that the result is `... .list = }` which leads to a compilation error even when `--disable-seccomp` is used. Can the code be modified to assign an empty list if all `#ifdef`s are undefined and/or not compile the code in the first place when `--disable-seccomp` is used? **Edit:** Sorry, I only searched in open issues, just found closed #1504.