-
Notifications
You must be signed in to change notification settings - Fork 13.3k
nostd libc not link #32661
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
Comments
@alexcrichton seemed to think this might be a bug in the libc crate around configs |
Looks like it's not linking to libc (the real one). There's a |
alexcrichton
added a commit
to alexcrichton/libc
that referenced
this issue
Apr 1, 2016
This crate currently relies on libraries being linked to come from libstd, but if `use_std` is disabled that's not true! In that case we need to pull in the libraries ourselves. Closes rust-lang/rust#32661
Yes this is currently a bug with the libc crate, and I've opened a PR: rust-lang/libc#249 |
bors
added a commit
to rust-lang/libc
that referenced
this issue
Apr 1, 2016
Link to libraries when disabling `use_std` This crate currently relies on libraries being linked to come from libstd, but if `use_std` is disabled that's not true! In that case we need to pull in the libraries ourselves. Closes rust-lang/rust#32661
alexcrichton
added a commit
to alexcrichton/libc
that referenced
this issue
Apr 4, 2016
This crate currently relies on libraries being linked to come from libstd, but if `use_std` is disabled that's not true! In that case we need to pull in the libraries ourselves. Closes rust-lang/rust#32661
bors
added a commit
to rust-lang/libc
that referenced
this issue
Apr 4, 2016
Link to libraries when disabling `use_std` This crate currently relies on libraries being linked to come from libstd, but if `use_std` is disabled that's not true! In that case we need to pull in the libraries ourselves. Closes rust-lang/rust#32661
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I tried this code:
I expected to see this happen:
Instead, this happened:
The text was updated successfully, but these errors were encountered: