Skip to content

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

Merged
merged 1 commit into from
Nov 29, 2017

Conversation

mwanner
Copy link
Contributor

@mwanner mwanner commented Nov 28, 2017

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 in nix-rust/nix#667.

Copy link
Contributor

@asomers asomers left a 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.

@alexcrichton
Copy link
Member

Thanks! Looks like CI is failing though?

@asomers
Copy link
Contributor

asomers commented Nov 28, 2017

The failure is due to a "line longer than 80 characters" error in the style checker.

@mwanner
Copy link
Contributor Author

mwanner commented Nov 29, 2017

Overly long lines corrected, CI now happy.

@alexcrichton
Copy link
Member

@bors: r+

@bors
Copy link
Contributor

bors commented Nov 29, 2017

📌 Commit 13ce9f8 has been approved by alexcrichton

@bors
Copy link
Contributor

bors commented Nov 29, 2017

⌛ Testing commit 13ce9f8 with merge ace4b86...

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
Copy link
Contributor

bors commented Nov 29, 2017

☀️ Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing ace4b86 to master...

@bors bors merged commit 13ce9f8 into rust-lang:master Nov 29, 2017
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
Copy link
Contributor

semarie commented Dec 17, 2017

#[deprecated()] seems to make problem when used in rustc.

see rust-lang/rust#46760 (comment)

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants