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: Christian Walther <email@hidden>
- Date: Sat, 10 May 2008 17:12:02 +0200
[Apologies for not replying in the original thread. Is there a
possibility to get the original message in e-mail form when one wasn't
subscribed to the list at the time it was posted? The message I'm
replying to is <http://lists.apple.com/archives/xcode-users/2008/Jan/msg00064.html
>.]
On Sun, 6 Jan 2008 10:50:12 -0800, 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:
#if defined(__ppc__) && !defined(__ppc64__) FILE *__stderrp; #endif
If anyone has any additional insight or ideas, we would certainly
appreciate the input.
I just ran into the same problem, and discovered a solution that some
may be interested in.
I found that the extraneous ___stderrp symbol comes from libgcc.
Apparently GCC 3.3 always links libgcc from its installation path, not
from the SDK, i.e. /usr/lib/gcc/darwin/3.3/libgcc.a is used instead
of /Developer/SDKs/MacOSX10.3.9.sdk/usr/lib/gcc/darwin/3.3/libgcc.a. I
have been able to remedy this by adding an OTHER_LDFLAGS_ppc build
setting containing "-L/Developer/SDKs/MacOSX10.3.9.sdk/usr/lib/gcc/
darwin/3.3" (without the quotes) to my project, and the product now
runs on 10.3.9.
-Christian
_______________________________________________
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