-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Linker fails to link rlibs on arm64_32-apple-watchos #103508
Comments
The |
"building for watchOS-arm64_32 but attempting to link with file built for unknown-arm64" does seem to indicate something awry somewhere. I had in your changes what is the |
Also, has stdlib support of watchos been merged yet? |
Yes, but it still requires nightly and -Zbuild-std due to not shipping watchOS builds via rustup.
It's completely identical to ios.rs, just renamed. It's basically what you did. I don't believe the issue is with the |
Does |
So definitely something is broken, I can no longer build target on current Rust master ( I am not sure what the problem is, but I think it might be due to I will try to look further, but about to start 5 days of vacation... |
I suspect this is unrelated given that the simulators work, and many of the errors pointing to a different thing. I do agree that probably
Enjoy your vacation, thanks for responding. |
#104361 was merged and it claimed to fix this. Can this be closed? |
In rust-random/getrandom#317 I tried to add watchOS and tvOS support to
getrandom
. During this process, I tried to do acargo test --no-run
build for watchOS, which gave me a long error output, seemingly indicating that the linker was ignoring rlibs:This seems to indicate that we aren't invoking the linker correctly on arm64_32-apple-watchos, or that it doesn't understand rlibs for some other reason. This is on macOS 13.0 and the SDKs from XCode 14.0.1. Perhaps that is related? I'm not sure.
CC @vladimir-ea, @deg4uss3r (listed as owners of that target on https://doc.rust-lang.org/nightly/rustc/platform-support/apple-watchos.html)
The text was updated successfully, but these errors were encountered: