Hi, I am getting a linking error when building my app to run against an iOS17 device, using Xcode15. Same project builds and runs fine with Xcode 14 and iOS16. The linking error just says:
clang: error: unable to execute command: Segmentation fault: 11 clang: error: linker command failed due to signal (use -v to see invocation)
Not sure what I should try to overcome this. I can't run my app on an iOS17 device. It builds, links and runs just fine on a simulator.
I have the same problem.
I have the same problem.
Getting the Same issue any one got an Answer?
I have the same problem.
Having the same problem.
There is an issue tracking this in the firebase-ios-sdk repo. I'm trying to figure out it if this is only caused by Firebase. Is anyone using Firebase? Is anyone not using Firebase, but seeing this issue?
If you are using Firebase and seeing this issue, please feel free to contribute to the discussion in the above linked issue. Additionally, reverting to Firebase 10.7.0 should unblock your development until a solution is found. Thanks!
Same issue.
other link flags add "-ld64"
I have the same problem.
I had a similar problem
Ld *** clang: error: unable to execute command: Segmentation fault: 11 clang: error: linker command failed due to signal (use -v to see invocation)
I see the same issue, no firebase in use. Filed as FB12236547. Adding -ld64 (using the old linker?) works fine for now.
other linker flags add "-ld64" ，works for me
Filed as
FB12236547.
Thanks.
using the old linker?
Yes, that’s what that flag does. I just updated An Apple Library Primer for some of the backstory to this.
This definitely looks like a bug in ld_prime. Regardless of whether or not the input library is malformed, the linker shouldn’t crash |-:
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
I have the same problem.
My issue had to do with some SPM repositories, and how they were being reset to v1.0 when set to "Exact Match" to an older version. This seems to be a bug with Xcode 15 Beta1 (FB12283412). Setting it 'Up to Major Version' from 1.0 to the last acceptable version worked for me.