-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Port #672 and #686 to musl. #699
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
Conversation
Looks like CI may be failing? |
It looks like offending syscalls were added in musl 1.16, you're using 1.15. |
Oh certainly! You can update the various scripts in |
It's looks like we've run into #665 on musl too:
|
Want to update them? |
It's not so easy. These constants are defined in |
Oh yeah that's fine, want to duplicate the definition and push them down the module hierarchy? |
The same will have to be added on x86 and x86_64 for Android. Maybe it would be better to simply generated them based on the installed libc? |
Duplication is fine, we're not going to be generating the libc crate based on what was found at compile time |
Why not?
|
Sorry this isn't really quite the PR to debate this on, that question is much broader than just this. If you'd like to land this then the best way will be to duplicate the definitions I believe, otherwise if you'd like to wait and hold off we can continue discussion on perhaps a dedicated issue. |
So let's land it with duplication for now and discuss it in a separate issue. |
They have been added in musl 1.16 but updating musl is non-trivial.
@bors: r+ |
📌 Commit 0ef465a has been approved by |
☀️ Test successful - status-appveyor, status-travis |
No description provided.