[macos] XCode 15 issues warnings for object files when linking #7941
Comments
|
We have an issue I need to report where the new linker generates bad object code on ARM. I mentioned it to Andrew. I doubt fixing this warning would fix the error in question as it is generating a straight up illegal instruction. |
|
More info on this ... apparently Apple wants LC_BUILD_VERSION to be set for all valid mach-o object files: rust-lang/rust#114114 |
alexreinking
added a commit
that referenced
this issue
Jun 25, 2024
This gives LLVM enough information to generate a "platform load-command" in the MachO object file. Fixes #7941
alexreinking
added a commit
that referenced
this issue
Jun 25, 2024
This gives LLVM enough information to generate a "platform load-command" in the MachO object file. Fixes #7941
alexreinking
added a commit
that referenced
this issue
Jun 25, 2024
This gives LLVM enough information to generate a "platform load-command" in the object file. Fixes #7941
alexreinking
added a commit
that referenced
this issue
Jun 25, 2024
This gives LLVM enough information to generate a "platform load-command" in the object file. Fixes #7941
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It appears XCode 15 now includes a custom (undocumented) version of LD which expects object files to be generated with a version number specified in the OS part of the LLVM target triple, otherwise it issues warnings like:
This appears to have hit the JuliaLang team too, and they discovered they had to update their target triple for AOT compilation to include the OS version:
JuliaLang/julia#51830
More discussion here:
JuliaLang/julia#51562
So, it appears we may need to update the LLVM object file output to include the darwin/macos minimum deployment version in the target triple to be compatible with XCode 15 and future Apple toolchains.
The text was updated successfully, but these errors were encountered: