-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
XCode 14 and older rustup installed rustc versions are incompatible #105167
Comments
I believe this is a known issue. It was fixed by #84449. I think the only workaround is to use an older xcode, or to use another linker. Rumors are that mold doesn't complain, though that might just be by luck. |
That might be that mold is based on an older version of apple's ld from before this breaking change. |
According to rust-lang/rust#105167 and rust-lang/rust#107252 (comment), Xcode 14 broke support for rustc < 1.53.
According to rust-lang/rust#105167 and rust-lang/rust#107252 (comment), Xcode 14 broke support for rustc < 1.53.
According to rust-lang/rust#105167 and rust-lang/rust#107252 (comment), Xcode 14 broke support for rustc < 1.53. Backport of commit 8dd37c5.
According to rust-lang/rust#105167 and rust-lang/rust#107252 (comment), Xcode 14 broke support for rustc < 1.53. Backport of commit 8dd37c5.
I don't expect this is actionable in rustc. For users hitting the "not mach-o or llvm bitcode file" error in GitHub Actions, the solution is to use |
With the update to xcode 14 older rustc versions installed from
rustup
are failing with an error that looks like this:From testing 1.54.0 and 1.56.0 and latest is fine, 1.51 and 1.53 are not.
Meta
rustc --version --verbose
:I believe this is related to #103044.
Since those are rather old Rust versions I assume there is not a lot of reason to do something about it, but I figured I report it because I wasn't sure if this was supposed to happen and maybe someone else will also stumble upon it. I noticed it because I had an override set to my MSRV on a library.
The text was updated successfully, but these errors were encountered: