Re: libc UNIX2003 mystery
Re: libc UNIX2003 mystery
- Subject: Re: libc UNIX2003 mystery
- From: Wim Lewis <email@hidden>
- Date: Tue, 7 Dec 2010 10:08:21 -0800
On 7 Dec 2010, at 9:28 AM, Andy O'Meara wrote:
> Hey guys, I was hoping an Xcode or OS guru can help nail this one... I've scoured the interwebs for an answer but I can't find a definitive answer, so I'm turning to the expertise here.
>
> We use CPython statically and have been using its prepackaged build script to build the static lib that we use. That lib gets included in our main project (a bundle actually) and all is well. However, when our bundle tries to load on a 10.4 machine, it fails and the system log says:
>
> Symbol not found: _fsync$UNIX2003 (libSystem.B.dylib)
These are "symbol variants":
http://developer.apple.com/library/mac/releasenotes/Darwin/SymbolVariantsRelNotes/index.html
My guess is that, somewhere, your build system is not passing the necessary -mmacosx-version-min flag to either a compile or a link step, and so the compiler is choosing variants available on 10.5+. Your description of what you're doing sounds like it should work, but maybe someone else will see the problem.
_______________________________________________
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