[GH-ISSUE #2229] Cross Compiling Difficulty #1498

New issue

Closed

opened 2026-05-05 08:10:02 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 08:10:02 -06:00

Owner

Originally created by @jreach-dev on GitHub (Oct 31, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2229

Due to firejails minimal dependencies and lightweight design, it is ideal for securing deeply embedded Linux components. Unfortunately it is difficult to cross compile.

Example:
Cross compiling fails because the make system creates a binary, then executes that binary as part of the build process. This naturally impairs cross compiling.

Solution A:
Compile with QEMU. This is very slow but it works great. Fully working samples have been produced for i.MX6 Ultra Lite.

Solution B:
Install QEMU but don't emulate compile with QEMU. Doesn't work because seccomp binary is not statically linked. This would be the ideal route for build automations like Yocto.

Solution C:
Disable seccomp. This works but I want seccomp!

Solution D:
Does the seccomp binary need to be run during the build process?

Solution E:
Compile on embedded host. Not really an option for the type of development I am doing.

What would the best approach to cross compiling be?

Originally created by @jreach-dev on GitHub (Oct 31, 2018). Original GitHub issue: https://github.com/netblue30/firejail/issues/2229 Due to firejails minimal dependencies and lightweight design, it is ideal for securing deeply embedded Linux components. Unfortunately it is difficult to cross compile. Example: Cross compiling fails because the make system creates a binary, then executes that binary as part of the build process. This naturally impairs cross compiling. Solution A: Compile with QEMU. This is very slow but it works great. Fully working samples have been produced for i.MX6 Ultra Lite. Solution B: Install QEMU but don't emulate compile with QEMU. Doesn't work because seccomp binary is _not_ statically linked. This would be the ideal route for build automations like Yocto. Solution C: Disable seccomp. This works but I want seccomp! Solution D: Does the seccomp binary need to be run during the build process? Solution E: Compile on embedded host. Not really an option for the type of development I am doing. What would the best approach to cross compiling be?

gitea-mirror closed this issue

2026-05-05 08:10:03 -06:00

gitea-mirror commented

2026-05-05 08:10:04 -06:00

Author

Owner

@jreach-dev commented on GitHub (Oct 31, 2018):

Sorry. Duplicate of #2044

@jreach-dev commented on GitHub (Oct 31, 2018): Sorry. Duplicate of #2044

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#1498

No description provided.

Rows
Columns