What do these Dsymutil Warnings mean in XCode 4.5?

Question

I am linking a static framework for iOS, against an armv7 ios 6 application, I suspect that the original binaries are from XCode 3.x and were compiled with GCC, and that I\'m no

Answer 1

I am on the other side of this, building a library for others to use, and I was able to alter the library project by setting 'GCC_GENERATE_DEBUGGING_SYMBOLS = NO' in the Build Settings to make those warnings go away in an Application project that consumed the output framework.

This isn't a solution to your problem, but if you're in contact with this vendor, you could pass this along.

Answer 2

These errors are to do with the architectures you are using and the resources you are referencing. I don't understand the reasons myself, but if you want them to go away, go to Build settings, then Build Options and then select Debug information format and select DWARF.

Answer 3

What I did was just delete the /Library/Developer/Xcode/DerivedData folder and it fixed everything for me.

Answer 4

The other answers contain helpful information but I wish to put the real answer down succinctly:

You can not fix this, and the meaning of the errors is simple: The current linker sees these library files as containing elements that can not be opened.

To solve the warnings, contact the vendor and get a recompiled library that has been rebuilt with a later version of CLANG.

Answer 5

Another reason these warnings could occur is because of incorrect symbol stripping settings for release builds in a project. Contact the author of the framework and tell them to make a new binary with the proper symbol stripping settings.