Re: 2.1->2.2 created link error: std::__ioinit
Re: 2.1->2.2 created link error: std::__ioinit
- Subject: Re: 2.1->2.2 created link error: std::__ioinit
- From: "Robert J. Lang" <email@hidden>
- Date: Sun, 13 Nov 2005 14:20:29 -0800
- Thread-topic: 2.1->2.2 created link error: std::__ioinit
on 11/12/05 11:54 AM, jkp at email@hidden wrote:
> I just posted to the Cocoa list (probably the wrong place actually)
> because Ive had exactly the same problem. <snip>
> ...what level of debugging symbols do you have turned on Robert?
-gfull.
on 11/12/05 12:38 PM, Eric Albert at email@hidden wrote:
> The easiest way to figure out where the reference is coming from is to
> add "-Wl,-Y,1000" to your Other Linker Flags. That'll tell the linker
> that for the first 1000 undefined symbols, it should print out the
> object file referencing them.
And so it does:
/Library/Caches/com.apple.Xcode.501/SharedPrecompiledHeaders/tmHeader-gfunlz
nupxtwafhgsuaenfzquikw/tmHeader.h.gch.o reference to undefined std::__ioinit
So the reference comes from a precompiled header file that #includes
<iostream>, among other things.
on 11/12/05 1:45 PM, Hugh Hoover at email@hidden wrote:
> I ran into the missing std::_ioinit problem too - I've tracked it
> down to the new "separate PCH Symbols" setting, which, if on,
> produces the problem, if off, no problem. std::__ioinit is defined
> in <iostream> (/Developer/SDKs/MacOSX10.4u.sdk/usr/include/c++/4.0.0/
> iostream)
Aha. Yes, turning off separate PCH worked for me. Thanks!
>
> So - the issue is apparently with static objects defined (not just
> declared) in a PCH. Is there some workaround for this (other than
> the obvious of turning off separate PCH...)?
Ditto.
_______________________________________________
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