Re: Weak linking for 10.2.8
Re: Weak linking for 10.2.8
- Subject: Re: Weak linking for 10.2.8
- From: "William H. Schultz" <email@hidden>
- Date: Tue, 18 Oct 2005 09:09:39 -0700
David,
If you are wanting to take advantage of new features of the OS, you
might as well select the current OS as the SDK. If you have 10.2.8
selected as the SDK, weak linking is nearly pointless, as 10.1.x
didn't support it, and the major selling feature of weak leaking is
that you get to take advantage of newer features while still offering
support for older OSes. Also, if you select the current OS as your
SDK, your existing errors go away. :D
Hank Schultz
Cedrus Corporation
http://www.cedrus.com/
On Oct 17, 2005, at 10:01 AM, David Dunham wrote:
At 16:36 -0400 05-10-14, Matt DeFoor wrote:
ld: Undefined symbols:
_sprintf$LDBL128
_vsnprintf$LDBL128
_atanf
_fprintf$LDBL128
_sscanf$LDBL128
I'm not using long double anywhere in my code that I'm aware of
(though it could be in some of my libraries). Where do I pick up
these symbols?
Try adding -lSystemStubs to your other linker flags to resolve
those undefined symbols.
FWIW, that generates its own error, about not finding the lib file.
It appears that the actual error here was caused by not compiling a
library with 3.3.
Unfortunately, now I'm back to trying to get that library to
compile, with the conflicting types for __mbstate_t error (caused
by /usr/include somehow getting into the search path, rather than
the SDK version).
--
David Dunham A Sharp, LLC
Voice/Fax: 206 783 7404 http://a-sharp.com
Efficiency is intelligent laziness.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40cedrus.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