-
Notifications
You must be signed in to change notification settings - Fork 23
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
if-watch does not compile on aarch64 #3
Comments
bors
referenced
this issue
in rust-lang/libc
Dec 3, 2020
Followup to #1649. When adding `nlmsghdr` for `musl` targets the `aarch64` arch was singled out, not getting the definition. This remedies the problem so that `if-watch` compiles on `aarch64-unknown-linux-musl`. - [0] https://github.com/dvc94ch/if-watch/issues/3
bors
referenced
this issue
in rust-lang/libc
Dec 3, 2020
Followup to #1649. When adding `nlmsghdr` for `musl` targets the `aarch64` arch was singled out, not getting the definition. This remedies the problem so that `if-watch` compiles on `aarch64-unknown-linux-musl`. - [0] https://github.com/dvc94ch/if-watch/issues/3
Released in 0.1.7 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When compiling if-watch on aarch64, you get the following error:
The immediate cause is the following: while the required structs have been added to some architectures, they have not yet been added to others.
So this would e.g. compile just fine for mips64, if anybody would still care about that arch...
Now, what I don't know is whether there is some fundamental reason why this mechanism is not available for aarch64, or if it is just that somebody has forgotten to update the platform specific headers.
What would need to be done would be to make a PR against https://github.com/rust-lang/libc, similar to rust-lang/libc#1649 , and then somehow try out that the mechanism actually works on aarch64.
Then we would have to wait for this to be merged, published, and included in musl, which we use in our build.
The text was updated successfully, but these errors were encountered: