Lorenzo

Hello there, any Status on this?

No, it isn't, `arm64-apple-darwin` isn't a valid target ``` [root@52bd9e36c736 be]# cargo build --target arm64-apple-darwin error: failed to run `rustc` to learn about target-specific information Caused by: process didn't exit...

Ah, got it, sorry I misunderstood. Btw I used o64-clang (for amd64 builds) instead of o64h-clang (for aarch64 builds) and somehow, it worked. ``` [root@52bd9e36c736 be]# CC=o64-clang RUSTFLAGS="-C linker=o64-clang -C...

for some weird reason, this works: ``` [root@52bd9e36c736 be]# CC=clang RUSTFLAGS="-C linker=o64h-clang -C link-args=-D__ARM_ARCH__" cargo build --target aarch64-apple-darwin Compiling ring v0.16.20 error: failed to run custom build command for `ring...

HMmmmmmmm

If anyone is having the same issue with o64h-clang, I started this issue https://github.com/tpoechtrager/osxcross/issues/333

Ok, for some weird reason this works: ``` [root@52bd9e36c736 be]# cargo clean [root@52bd9e36c736 be]# CFLAGS="-D__ARM_ARCH__" CC=clang RUSTFLAGS="-C linker=o64h-clang" cargo build --target aarch64-apple-darwin Compiling cc v1.0.73 Compiling untrusted v0.7.1 Compiling ring...

any ideas?

Well clang was 13 and the os i tested was arch Linux container but it also doesn't work in Ubuntu, Manjaro and fedora with MacOS SDK 11.3

I was compiling a project in rust that had dependency in ring which is the crate broke the build. Btw starting the compilation with system clang fails but then switching...