Re: Undefined symbols: "_fputs$UNIX2003", referenced from:
Re: Undefined symbols: "_fputs$UNIX2003", referenced from:
- Subject: Re: Undefined symbols: "_fputs$UNIX2003", referenced from:
- From: Rich Collyer <email@hidden>
- Date: Tue, 4 Nov 2008 09:35:08 -0800
A couple of weeks ago, I initiated the thread about $UNIX2003 linker
issues. Since then, I tried to convert to use the openssl that comes
with the Mac, but according to AppleDTS, they don't support
dynamically loaded crypto engines (which is a product requirement for
me). So I am back to this issue, which was never fully resolved.
What I have learned is that when I build openssl with XCode 3.0, it
contains a reference to _fputs$UNIX2003, but does not complain about
it when I statically link the libcrypto.a file with my application.
When I build openssl with XCode 3.1, it also contains a reference to
_fputs$UNIX2003, but does complain about it when I statically link the
libcrypto.a file with my application.
I read the Apple document "Symbol Variants: Why Those Dollar Signs?",
which was helpful in understanding what is happening, but really
difficult to understand how to fix the problem. I tried to add a
number of -U and -D flags to the build, but that seemed to make
matters worse.
What has changed that makes XCode 3.1 make this an error, when XCode
3.0 considers this OK. Is one of them just wrong? Is there an update
to the recommended scripts listed in the Apple Document "Building an
Open Source Universal Binary" that would ensure that the library is
built to work with 10.4 and beyond?
+++++++++++++++++++++++
Rich Collyer
Senior Software Engineer
IronKey, Inc.
email@hidden
+++++++++++++++++++++++
On Oct 13, 2008, at 5:18 PM, Nick Zitzmann wrote:
On Oct 13, 2008, at 5:23 PM, Rich Collyer wrote:
This makes sense, but from what I can tell, it is being build
against 10.4
setenv MACOSX_DEPLOYMENT_TARGET 10.4
setenv SDKROOT /Developer_31/SDKs/MacOSX10.4u.sdk
setenv SDK_DIR /Developer_31/SDKs/MacOSX10.4u.sdk
setenv SDK_NAME macosx10.4
Well, you're linking against some libcrypto that was built with the
10.5 SDK, since the linker error you're getting should not be
happening if it was built against an older SDK.
Nick Zitzmann
<http://seiryu.home.comcast.net/>
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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