-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Define SO_INCOMING_CPU for {aarch64,x86_64}-unknown-linux-musl #2119
Conversation
r? @JohnTitor (rust-highfive has picked a reviewer for you, use r? to override) |
Thanks! |
📌 Commit a045c09 has been approved by |
☀️ Test successful - checks-actions, checks-cirrus-freebsd-11, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13 |
Any plans to release a version including this soon? I'm currently blocked by this as the regression was part of a patch release. |
Bump to 0.2.91 I'm going to make a new release as requested by #2119 (comment). r? `@ghost`
@timvisee Published 0.2.91. |
Define SO_INCOMING_CPU for i686-unknown-linux-gnu Hi! Following the example from #2119, I've tried adding the constant to i686-unknown-linux-gnu as well to fix a similar issue.
Define SO_INCOMING_CPU for i686-unknown-linux-musl Following the examples from #2119 and #2123, to fix the same issue with `socket2`: rust-lang/socket2#213
Define SO_INCOMING_CPU for i686-unknown-linux-musl Following the examples from #2119 and #2123, to fix the same issue with `socket2`: rust-lang/socket2#213
This continues where #2115 left off and hopefully fixes
socket2
crate on these two targets.