You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I want to link statically to e.g. Android libc, the libc crate will ignore the +crt-static request and will link libc dynamically anyway.
The libc crate should respect user requests like this and link to libc statically in #[cfg(target_feature = "crt-static")] mode if the target provides a static version of libc at all.
Static libc may require additionally linking some startup objects etc, and for some targets this is supported implicitly by rustc, but such support is not critical because the necessary linking can be done explicitly by the user with -C link-args and similar options.
The text was updated successfully, but these errors were encountered:
If I want to link statically to e.g. Android libc, the libc crate will ignore the
+crt-static
request and will link libc dynamically anyway.The libc crate should respect user requests like this and link to libc statically in
#[cfg(target_feature = "crt-static")]
mode if the target provides a static version of libc at all.The relevant code is here:
libc/src/unix/mod.rs
Lines 295 to 357 in bcbfeb5
Static libc may require additionally linking some startup objects etc, and for some targets this is supported implicitly by
rustc
, but such support is not critical because the necessary linking can be done explicitly by the user with-C link-args
and similar options.The text was updated successfully, but these errors were encountered: