Re: link problem producing universal binary
Re: link problem producing universal binary
- Subject: Re: link problem producing universal binary
- From: Chris Espinosa <email@hidden>
- Date: Sat, 6 Jan 2007 15:18:00 -0800
On Jan 6, 2007, at 3:12 PM, Paul Forgey wrote: I have a project which works fine for debugging on my local machine using ZeroLink. If I try to build a release build as a universal binary, I get a link error (path names partially redacted):
/usr/bin/ld: multiple definitions of symbol .objc_class_name_Dissector .../ppc/AppDelegate.o definition of absolute .objc_class_name_Dissector (value 0x0) .../ppc/Dissector.o definition of absolute .objc_class_name_Dissector (value 0x0) .../ppc/ARPDissector.o definition of absolute .objc_class_name_Dissector (value 0x0)
I've checked in the build output that all modules are only being linked once. I can find nothing in common with these three source files that could cause this. There are no duplicated source files in the project either.
Do the three sources (AppDelegate.m, Dissector.m, ARPDissector.m) include a common header file, and if so, what's in it? You may be declaring an implementation of the class Dissector in its header, instead of just its interface.
Note that ZeroLink, by skipping the link step entirely, also suppresses all link errors of this nature, turning them into runtime errors or other odd behavior. That the link problem doesn't happen with ZeroLink but does in a Release build is to be expected.
Chris |
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden