Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get "Bad system call" when compiling a Cython module #154

Open
Techcable opened this issue Mar 11, 2021 · 1 comment
Open

Get "Bad system call" when compiling a Cython module #154

Techcable opened this issue Mar 11, 2021 · 1 comment
Labels
syscall/seccomp Issues related to syscalls / seccomp

Comments

@Techcable
Copy link

Cython is a DSL for writing native python extension modules.

Running "cython" seems to fail with a "bad system call" message during the cython -> C translation. If I run with a manual makepkg this problem doesn't exist and everything works fine, so it must have something to do with the process-jail.

Here are some AUR packages that trigger the issue:

  1. python-scikit-image
  2. python-pywavlet

Thanks for your time! 😄

@vn971
Copy link
Owner

vn971 commented Mar 25, 2021

Hi @Techcable! I'm a bit uncertain myself on what to do here. Seems that there are some packages, even though rare, that require syscalls that could otherwise be considered as dangerous / strange to have in a build. Possibly the situation will improve if the syscall list could be altered or temporarily ignored.

Would e.g. building an ignore flag be something you'd consider contributing?

@vn971 vn971 added the syscall/seccomp Issues related to syscalls / seccomp label Mar 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
syscall/seccomp Issues related to syscalls / seccomp
Projects
None yet
Development

No branches or pull requests

2 participants