Re: Build on 10.5.1, run on 10.3.5, undefined symbols (solved, sort of)
Re: Build on 10.5.1, run on 10.3.5, undefined symbols (solved, sort of)
- Subject: Re: Build on 10.5.1, run on 10.3.5, undefined symbols (solved, sort of)
- From: Stevo Brock <email@hidden>
- Date: Mon, 7 Jan 2008 13:28:40 -0800
We actually do need 10.3.5. Our apps work back to 10.3 as, for us,
that represents the sweet spot between OS features and market
potential. Many of our customers are pro-audio folks who have set up
rather sophisticated studios and updating even one piece for them
requires re-validation of their system at the least, and possible a
waterfall of other software/hardware upgrades as well. Therefore,
once they get a good system running, they don't upgrade for a long
time. In fact, we have many folks that we talk to that are still on
OS 9 because it works and updating would require major upgrades and
major $$$.
In the 10.4 days, everything was working just fine. The real issue
here is moving our dev env. from 10.4 to 10.5. At face value it's
supposed to "just work", and the way it's supposed to "just work" is
to set your deployment target. The reality is that there are actually
hidden hoops you have to go through to really get it to work (the ones
I know about I put in my last e-mail). The latest for us is that
something somewhere in our app is still referencing ___stderrp, and I
can't find it.
-Stevo Brock
Head of Development
Monkey Tools, LLC
www.monkey-tools.com
On Jan 6, 2008, at 2:05 PM, Steve Checkoway wrote:
On Jan 6, 2008, at 1:57 PM, Steve Checkoway wrote:
On Jan 6, 2008, at 10:50 AM, Stevo Brock wrote:
However, even with this, and checking every object and library
that is linked, somehow we still have a mysterious reference to
___stderrp. i.e. I have run "nm | grep stderr" on all the linked
object files and libraries and find no reference, however running
the same on the final app file reveals a reference. We have added
the following line to resolve the runtime error:
__stderrp is defined in libSystem.dylib. Are you not linking
against the standard libraries for some reason?
Sorry, somehow I missed the whole point. You're compiling for
10.3.5? Do you mean 10.3.9, the update to 10.3.9 was free, there's
no reason not to require it. Then you can build with gcc 4, which
I'm assuming doesn't have the problem you mentioned.
--
Steve Checkoway
"Anyone who says that the solution is to educate the users
hasn't ever met an actual user." -- Bruce Schneier
_______________________________________________
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
_______________________________________________
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
| References: | |
| | >Build on 10.5.1, run on 10.3.5, undefined symbols (From: Stevo Brock <email@hidden>) |
| | >Re: Build on 10.5.1, run on 10.3.5, undefined symbols (From: Ken Thomases <email@hidden>) |
| | >Re: Build on 10.5.1, run on 10.3.5, undefined symbols (solved, sort of) (From: Stevo Brock <email@hidden>) |
| | >Re: Build on 10.5.1, run on 10.3.5, undefined symbols (solved, sort of) (From: Steve Checkoway <email@hidden>) |
| | >Re: Build on 10.5.1, run on 10.3.5, undefined symbols (solved, sort of) (From: Steve Checkoway <email@hidden>) |