Re: link problem producing universal binary
Re: link problem producing universal binary
- Subject: Re: link problem producing universal binary
- From: Paul Forgey <email@hidden>
- Date: Sat, 6 Jan 2007 15:26:44 -0800
crap.. I accidentally #imported an .m file.
On Jan 6, 2007, at 3:22 PM, Paul Forgey wrote:
On Jan 6, 2007, at 3:18 PM, Chris Espinosa wrote:
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?
Yes, Dissector.h, as do tens of other source files.
You may be declaring an implementation of the class Dissector in
its header, instead of just its interface.
Nope.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40aphrodite.com
This email sent to email@hidden
_______________________________________________
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