-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Use IFF_OACTIVE and IFF_RUNNING even on FreeBSD. Deprecate the DRV ones. #859
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
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.
Yep, that's what I meant.
Thanks! Looks like CI is failing though? |
The failure is due to a "line longer than 80 characters" error in the style checker. |
8a67ed1
to
13ce9f8
Compare
Overly long lines corrected, CI now happy. |
@bors: r+ |
📌 Commit 13ce9f8 has been approved by |
Use IFF_OACTIVE and IFF_RUNNING even on FreeBSD. Deprecate the DRV ones. According to @asomers, libc should propagate the use of the portable constants `IFF_OACTIVE` and `IFF_RUNNING` for user-space applications, instead of `IFF_DRV_OACTIVE` and `IFF_DRV_RUNNING`. It least that's my understanding of [his comment](nix-rust/nix#667 (comment)) in nix-rust/nix#667.
☀️ Test successful - status-appveyor, status-travis |
The libc crate started using the #[deprecated] attribute, which is not supported on Rust 1.8.0 stable, and results in a compile error. This change was presumably introduced in commit 13ce9f8 [1] as part of pull request 859 [2]. The solution is to put Cargo.lock under source control and freeze all dependency versions, to be more resilient to external changes. [1]: rust-lang/libc@13ce9f8 [2]: rust-lang/libc#859
|
According to @asomers, libc should propagate the use of the portable constants
IFF_OACTIVE
andIFF_RUNNING
for user-space applications, instead ofIFF_DRV_OACTIVE
andIFF_DRV_RUNNING
. It least that's my understanding of his comment in nix-rust/nix#667.