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

redox_syscall no longer appropriate? #271

Closed
mightyiam opened this issue Jan 30, 2024 · 1 comment · Fixed by #272
Closed

redox_syscall no longer appropriate? #271

mightyiam opened this issue Jan 30, 2024 · 1 comment · Fixed by #272

Comments

@mightyiam
Copy link

That said, redox_syscall is no longer meant to be used anywhere except for low-level userspace components like relibc and drivers, as Redox doesn't guarantee a stable syscall ABI. Instead, the libredox crate is recommended

This is from the private Redox OS/Dev Matrix room.

@Stebalien
Copy link
Owner

We don't actually use it for low-level syscalls, just to get the ENOSYS constant for errors. But it looks like I can just get that from rustix (through libc) so I'll drop the dep.

Stebalien added a commit that referenced this issue Jan 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants