Skip to content

rfc 1291: Add libutil to scope of libc crate on Linux #1529

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Mar 31, 2016
Merged

rfc 1291: Add libutil to scope of libc crate on Linux #1529

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions text/1291-promote-libc.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -166,9 +166,9 @@ In order to have a well defined scope while satisfying these constraints, this
RFC proposes that this crate will have a scope that is defined separately for
each platform that it targets. The proposals are:

* Linux (and other unix-like platforms) - the libc, libm, librt, libdl, and
libpthread libraries. Additional platforms can include libraries whose symbols
are found in these libraries on Linux as well.
* Linux (and other unix-like platforms) - the libc, libm, librt, libdl,
libutil, and libpthread libraries. Additional platforms can include libraries
whose symbols are found in these libraries on Linux as well.
* OSX - the common library to link to on this platform is libSystem, but this
transitively brings in quite a few dependencies, so this crate will refine
what it depends upon from libSystem a little further, specifically:
Expand Down