GenerateDSYMFile warning: unable to open object file

Question

The background: I have a project that I last built on 10.5 on a PPC computer using xcode v3.1. It builds against the 10.4 SDK. I now have a MacBook with 10.6 on it and Xcode v3.2.1. I installed the 10.4 SDK with xcode. So now I want to build the project on an intel chip on 10.6. I first get a build error because I have the wrong version of gcc setup so I change the build settings to use gcc 4.0.

The problem: Now when I build the project I get the following warning: GenerateDSYMFile "build/Release/What's Keeping Me?.app.dSYM" "build/Release/What's Keeping Me?.app/Contents/MacOS/What's Keeping Me?" cd "/Users/hmcshane/Development/ Cocoa Projects/What's Keeping Me?" /Developer/usr/bin/dsymutil "/Users/hmcshane/Development/ Cocoa Projects/What's Keeping Me?/build/Release/What's Keeping Me?.app/Contents/MacOS/What's Keeping Me?" -o "/Users/hmcshane/Development/ Cocoa Projects/What's Keeping Me?/build/Release/What's Keeping Me?.app.dSYM"

warning: (i386) /Users/hmcshane/Downloads/Csu-71/crt.dynamic_no_pic.o unable to open object file warning: (ppc7400) /Users/hmcshane/Downloads/Csu-71/crt.dynamic_no_pic.o unable to open object file

Any idea what this is? And why is the path for the problem files rooted in my downloads folder? The project certainly doesn't reside there.

Answer 1

I see the annoyed warnings after upgrading to Xcode 4.5. Then I tried changing Build Settings/Debug Information Format value from DWARF with dSYM file to DWARF and every relative warning disappeared :)

Answer 2

I had the same issue on iPhone, when building a projet that linked against custom static libraries. I seems XCode complains because it can't find debug infos for some of the linked objects.

I fixed the problem by disabling "Perfom Single-Object Prelink" in the library build settings.

I don't know how well this solution applies to the initial issue, but as this page is the first Google answer…