-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Always depends on std when built with cargo #14
Comments
Unfortunately this crate isn't really intended to be used in the |
Gah sorry hit the button too soon. To elaborate, this crate isn't intended to be used as part of the Stay tuned though, with rust-lang/rfcs#1184 implemented we'll definitely mark this as |
Thanks for being so helpful with difficult freestanders like me, @alexcrichton. 😄 |
Add SO_REUSEPORT for macos
Make binutils build (it is probably not fully functional)
The following lines mean that
libc
always depends onstd
when built withcargo
...#![cfg_attr(not(feature = "cargo-build"), no_std)]
...
... which doesn't work when using
cargo
with ano_std
crate and an alternative target (without a cross-compiledstd
crate, but that's ultimately not what I want anyway).In an attempt to hack around this, I added the following to my
Cargo.toml
:But this is the build command line:
Part of the challenge here is that the
libc
crate is just a slim wrapper around the Rust'sliblibc
, so changing things is probably difficult.Thoughts or suggestions, though? Should I not use the
libc
crate at all?The text was updated successfully, but these errors were encountered: