-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Make fails when attempting to compile for various Apple & iOS targets #42084
Comments
rustbuild refers to the [Not about the bug] Nowadays you don't need to build a cross-compiler from source yourself. curl https://sh.rustup.rs -sSf | sh and the whole "Building a Cross Compiler" should be replaced by rustup target add aarch64-apple-ios
rustup target add armv7-apple-ios
rustup target add armv7s-apple-ios
rustup target add x86_64-apple-ios
rustup target add i386-apple-ios then go on from "Hello, World: Building the Rust Library" (but ignore the cc @jgallagher |
Oh awesome thanks @kennytm that should make things much easier. |
curl https://sh.rustup.rs -sSf | sh
and the whole "Building a Cross Compiler" should be replaced by
rustup target add aarch64-apple-ios
rustup target add armv7-apple-ios
rustup target add armv7s-apple-ios
rustup target add x86_64-apple-ios
rustup target add i386-apple-ios work for me, thanks! |
I am getting |
@ppamorim All 32-bit Apple targets have been removed since 1.42.0. You could just leave those targets out. See https://blog.rust-lang.org/2020/01/03/reducing-support-for-32-bit-apple-targets.html for details. |
Triage: There is nothing to be done here, so I suggest that we close this issue, and direct questions to the users forum. |
I am trying to follow this guide
It's a little outdated but I have checked out repo in order to manually compile for these targets.
I have run:
However I think the ordering in the makefile is wrong as it tries to run an install.sh that does not exist.
rust-compile-log.txt
Log of failed installation is attached with the main issue being:
The text was updated successfully, but these errors were encountered: