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
AFAIK this crate has never read that env var, it's always expected CC to be set
Ahh, yes, cc now reads CC_aarch64_linux_android (i.e. CC_TARGET) only, I guess?
As mentioned in #459, CARGO_TARGET_AARCH64_LINUX_ANDROID_LINKER affected the build with cc previously. And the behavior for that certainly changed between 1.0.52 and 1.0.53.
Thanks for clarifying, I'm going to close this as there's no actionable item here :)
I've found
cc
>=1.0.53
doesn't seem to respectCARGO_TARGET_{TARGET_TRIPLE}_LINKER
.In the
libc
crate, e passaarch64-linux-android28-clang
asCARGO_TARGET_AARCH64_LINUX_ANDROID_LINKER
here: https://github.com/rust-lang/libc/blob/4d0643b769a4c1051908419e3cf25e6b46762dea/ci/docker/aarch64-linux-android/Dockerfile#L30-L33But the test emits this failure (full log: https://github.com/rust-lang/libc/runs/1266042807?check_suite_focus=true):
This means the build uses
aarch64-linux-android21-clang
, i.e., API 21 NDK.I think #495 is the cause since it's released as
1.0.53
, cc @Dushistov.The text was updated successfully, but these errors were encountered: