-
Notifications
You must be signed in to change notification settings - Fork 331
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
SPM build fails with undefined symbol "___llvm_profile_runtime" #906
Comments
cc @migs647 |
@TizianoCoroneo I may need some more information on your build configuration.
If you could put together a demo project that I could use to replicate that would be helpful. I think I'm going down a happy path and not seeing this. |
Small project that reproduces the issue. I just turned on Gather code coverage in the scheme settings. |
@TizianoCoroneo Thanks so much, diving into it. |
@TizianoCoroneo We have come to the same conclusion this is a bug with Apple. We suggest disabling the code coverage for now unless you can get the |
@TizianoCoroneo Is it possible you can try our current master branch? We changed up our Package.swift to allow swift package to determine to build as dynamic or static. We will put out 4.0.2 soon, but in the mean time you can try that. |
It works now, thank you! |
I recently stumbled with this issue using SPM, 4.1.6 version of Segment. I've try stuff like adding the
@migs647 Was 4.0.2 supposed to solve this issue? Not sure what to do. I don't really want to disable coverage. |
@TizianoCoroneo do you remember doing anything on your side to make this work? |
No, updating the package was enough. Code coverage works correctly for me now |
iOS Builds using the 4.0.1 prerelease fail with the following error:
This SO question seems relevant: looks like if you have code coverage enabled in your project SPM will inject this flag. I'm not sure if it is something that we could report to Apple, could you give a look?
https://stackoverflow.com/questions/58127940/undefined-symbols-llvm-profile-runtime
The text was updated successfully, but these errors were encountered: