|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
After more searching I found that some people have worked around this problem by including libSystemStubs.a. I tried it and it did resolve the link problems. And initial testing of the resulting applications look good.
Unfortunately in our case we want to provide gcc 4.0 static libraries to customers who might want to build against gcc 3.3. So I guess we'll have to teach them to include libSystemStubs.a when building under gcc 3.3.
But honestly I don't know what libSystemStubs.a is for or whether including it in a gcc 3.3 build is in fact the right work around. Frankly it would be nice to have a better understanding of the interrelationships between gcc 3.3 and 4.0 static libraries. Maybe someone from Apple would care to comment?
If this has been covered before or is documented elsewhere and I missed it, then I apologize.
Allen Cronce wrote:
_______________________________________________ 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
|>Error linking in Xcode 2.1 (undefined symbols in libSystem) (From: Dragan Milić <email@hidden>)|
|>Fwd: Error linking in Xcode 2.1 (undefined symbols in libSystem) (From: Dragan Milić <email@hidden>)|
|>Re: Fwd: Error linking in Xcode 2.1 (undefined symbols in libSystem) (From: Allen Cronce <email@hidden>)|
Visit the Apple Store online or at retail locations.
Copyright © 2011 Apple Inc. All rights reserved.