-
Notifications
You must be signed in to change notification settings - Fork 67
haiku: Fix sockaddr_in/sockaddr_in6; Solves #108 #109
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
Historic information I was able to dig up: sin_zero is 24 under Haiku because our network stack was originally based on the BeOS "bone" network stack circa 2001. The sin_zero was an early attempt at preperation for IPv6 before the common tatic of appending 6 in the POSIX api's. (they were expecting ipv6 to use sockaddr_in instead of making a new sockaddr_in6) @pfmooney I know time is running out on these crates... but a lot of stuff still references net2-rs and a broken net2 create means a lot doesn't compile under Haiku. Thanks! |
Oh.. I just got word something simular was just fixed in socket2-rs: |
Deprecated means we won't be merging feature additions or big refactors (if we can help it), but fixes like are absolutely covered under the mission of sustaining maintenance. Thanks for submitting it with all the context info |
Ah. Thanks for the clairification! I saw the new deprecrated owner and was wondering if it was a march towards the repo being read-only. Let me know if you see anything off here. Thanks for maintaining these old but important crates! |
src/socket.rs
Outdated
#[cfg(target_os = "haiku")] | ||
sin_zero: [0; 24], | ||
#[cfg(not(target_os = "haiku"))] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry to pick a style nit like this, but would you mind swapping the order on these, so the more common not-haiku comes first in the order?
No worries :-) Done. Thanks! |
Thanks. Are you looking for a release after this, or are there other haiku-related fixes you might have in the pipeline? |
nothing else really at the moment. To be honest, i'm not really sure how these fixes got missed. I'm pretty sure Haiku was Haiku is at Rust 1.48.0, so the port is pretty recent. I think we're cross-compiling our rust toolchain from Linux still though... not sure why. (i can dig into that) https://github.com/haikuports/haikuports/blob/master/dev-lang/rust_bin/rust_bin-1.48.0.recipe |
Released in v0.2.37 |
Bugfix only, solves final remaining build issues under Haiku (a new Rust platform)