Uh oh!
There was an error while loading. Please reload this page.
Use IFF_OACTIVE and IFF_RUNNING even on FreeBSD. Deprecate the DRV ones. - #859
Merged
Conversation
alexcrichton
commented
Nov 28, 2017
Member
Thanks! Looks like CI is failing though? |
asomers
commented
Nov 28, 2017
Contributor
The failure is due to a "line longer than 80 characters" error in the style checker. |
mwannerforce-pushed
the
freebsd-drop-drv
branch
from
November 28, 2017 22:18
8a67ed1 to
13ce9f8Comparemwanner
commented
Nov 29, 2017
ContributorAuthor
Overly long lines corrected, CI now happy. |
alexcrichton
commented
Nov 29, 2017
Member
@bors: r+ |
bors
commented
Nov 29, 2017
Contributor
📌 Commit 13ce9f8 has been approved by |
bors
commented
Nov 29, 2017
Contributor
bors added a commit
that referenced
this pull request
Nov 29, 2017
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.
bors
commented
Nov 29, 2017
Contributor
☀️ Test successful - status-appveyor, status-travis |
ruuda added a commit
to ruuda/thread-id
that referenced
this pull request
Dec 9, 2017
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
semarie
commented
Dec 17, 2017
Contributor
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
According to @asomers, libc should propagate the use of the portable constants
IFF_OACTIVEandIFF_RUNNINGfor user-space applications, instead ofIFF_DRV_OACTIVEandIFF_DRV_RUNNING. It least that's my understanding of his comment in nix-rust/nix#667.