Re: Linking Problem with 10.3.9 sdk

Subject: Re: Linking Problem with 10.3.9 sdk

From: Sarah Carruthers <email@hidden>

Date: Thu, 2 Feb 2006 08:36:45 -0800

Delivered-to: email@hidden

Chris,

Thanks for the reply.

I'm not sure if I understand why I can build and link using gcc 4.0 and 10.3.9 sdk (I'm linking with my versions of zlib and libpng that I've built myself using gcc 4.0), but my plugin still fails to load. Are you saying that zlib and libpng built with gcc 4.0 will link successfully, but fail to work at runtime?

If so, why does my plugin fail to reach it's entry point when I attempt to debug it? Sorry if these are dumb questions.

Should it work to build using gcc 3.3 and the 10.3.9sdk, and link with the libpng and zlib libraries that are built with gcc 3.3? I seem to recall trying this, and I ended up with build errors like the ones I mentioned in my original post:

ld: Undefined symbols:

_sprintf$LDBLStub

_fprintf$LDBLStub

Does this mean that I need to link explicitly with the a version of libSystemStubs.a built with gcc 3.3? If so, where would I find one? The only ones I have on my system are in the 10.3.9 sdks and 10.4u sdk, and I'm assuming that they were built with gcc 4.0.

Sarah

On 1-Feb-06, at 8:11 PM, Chris Espinosa wrote:

On Feb 1, 2006, at 4:05 PM, Sarah Carruthers wrote:

I recompiled zlib and libpng with gcc 4.0, and successfully built and linked my plugin with the 10.3.9sdk. However, my plugin (a vst audio plugin) now fails to load. As an experiment, I tried building it against the 10.2 sdk using gcc 3.3 (and zlib and libpng that are also built with gcc 3.3). And it loads successfully.
Is it possible that somehow the entry point of my plugin is being mangled when built with gcc 4.0?

You can't deploy to Mac OS X 10.2.8 (or anything earlier than 10.3.9) if you build with gcc 4.0. If you want to deploy to 10.2.8, you have to build with gcc3.3 and either the 10.3.9 SDK or the 10.2.8 one. If building with the 10.3.9 SDK, you may need to specifically link against the 10.2.8 versions of certain libraries like zlib, because they don't support the automatic weak linking features that Carbon and Cocoa do.

Chris
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden

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: http://lists.apple.com/mailman/options/xcode-users/email@hidden This email sent to email@hidden

Follow-Ups:

Re: Linking Problem with 10.3.9 sdk
- From: Fritz Anderson <email@hidden>

References:
	>Re: Linking Problem with 10.3.9 sdk (From: "E. Wing" <email@hidden>)
	>Re: Linking Problem with 10.3.9 sdk (From: Sarah Carruthers <email@hidden>)
	>Re: Linking Problem with 10.3.9 sdk (From: Chris Espinosa <email@hidden>)