Swinject: Undefined symbols for architecture x86_64: ___llvm_profile_runtime

[andriko13]

I'm getting an issue linking Swinject framework into my project when using Xcode9 and Swift3.2

It's giving me the following error:

Undefined symbols for architecture x86_64:
  "___llvm_profile_runtime", referenced from:
      ___llvm_profile_runtime_user in Swinject(SpinLock.o)
      ___llvm_profile_runtime_user in Swinject(Assembler.o)
      ___llvm_profile_runtime_user in Swinject(ObjectScope.Standard.o)
      ___llvm_profile_runtime_user in Swinject(ServiceEntry.o)
      ___llvm_profile_runtime_user in Swinject(SynchronizedResolver.o)
      ___llvm_profile_runtime_user in Swinject(DebugHelper.o)
      ___llvm_profile_runtime_user in Swinject(InstanceStorage.o)
      ...
     (maybe you meant: ___llvm_profile_runtime_user)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Getting this error with both 2.1.1 and 2.0.0 stable releases

[evisoup]

Try cleaning up the project. Also, release for Xcode9 and Swift3.2 is not out yet.

[andriko13]

Tried cleaning project, derived data, etc. to no avail.
I understand the release isn't out yet; just wanted to make sure this issue is tracked.

[yoichitgy]

@andriko13, how did you install Swinject? With Carthage or CocoaPods?

[Timmmm]

This is related to profiling. I get the exact same error in a different project when compiling with -fprofile-instr-generate. No idea why yet - I guess Clang is not linking with some require runtime library but I can't work out which one.

[Timmmm]

Ah, found the problem. If you pass -fprofile-instr-generate during compilation, but not during linking, Clang won't link with the appropriate libraries and you get this error.

[jakubvano]

@andriko13 is your original issue related to what @Timmmm is describing? If that is the case, and I understand it correctly, this is not the issue with the Swinject, but rather with specific project settings.

[Reflejo]

The reason why this is failing is because codeCoverageEnabled is set to YES on the test target (seems to be a bug on Xcode when linking statically). Removing that setting on Swinject fixes the problem.

For what is worth, passing -fprofile-instr-generate is only recommended on sim builds.

[jakubvano]

Closing due to inactivity

[ansonj]

I found this issue through a DuckDuckGo search for "undefined symbol llvm profile runtime". The issue does seem to occur when:

• You're building a test target for some project
• The project's test target does not have code coverage enabled
• The project includes a static framework whose test target _does_ have coverage enabled

Another fix that worked for me (not related to Swinject in particular) is to enable code coverage on the super-project. This way, the included framework can continue using code coverage during development.

[CLoutas]

This appears to be breaking SwiftUI's Preview by complaining that ___llvm_profile_runtime_user was not found for architecture x86_64. As @Reflejo mentioned, turning code coverage off fixes it.