• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: 2.1->2.2 created link error: std::__ioinit
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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: Sat, 12 Nov 2005 11:56:40 -0800
  • Thread-topic: 2.1->2.2 created link error: std::__ioinit

Hi Eric,

Thanks for the quick answer. I created my project originally in Xcode 2.1,
so *everything* was originally built with gcc 4.0.

It does use external static libraries (wxWidgets), but I rebuilt those
libraries, too, after upgrading to Xcode 2.2. And even if I remove the
static libraries from my project, the std::__ioinit undefined error is still
there. So it looks like it must come from the files within the project
(and/or their included headers).

Trying to track if it's included via some header, the Finder and Spotlight
can't find "__ioinit" in any file in a computer-wide search. Similarly, a
search through all project files and frameworks from within Xcode didn't
turn anything up.

Any more suggestions would be greatly appreciated.

Robert

on 11/11/05 8:36 PM, Eric Albert at email@hidden wrote:

> On Nov 11, 2005, at 6:09 PM, Robert J. Lang wrote:
>
>> I upgraded from Xcode 2.1 to Xcode 2.2, and a project that formerly
>> built in
>> all configurations now fails to link, with the sole link error being
>> that
>> symbol std::__ioinit is now undefined. Any thoughts on how to proceed?
>
> A quick check (admittedly on 10.3.9, not Tiger or Xcode 2.2, but this
> should hold true anyway) shows that std::__ioinit was defined in
> libstdc++.a, but it isn't part of libstdc++.dylib.  The .a is used when
> building with gcc 3.3 or later, while the dylib is used with gcc 4.0.
>
> That leads me to guess that there's a static library in your project
> that hasn't been rebuilt with gcc 4.0, part of your project is building
> with 3.3 and another part is building with 4.0, or you've inadvertently
> switched compiler versions for your project as part of moving to Xcode
> 2.2.
>
> Hope this helps,
> Eric
>
>


 _______________________________________________
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

  • Follow-Ups:
    • Re: 2.1->2.2 created link error: std::__ioinit
      • From: Hugh Hoover <email@hidden>
    • Re: 2.1->2.2 created link error: std::__ioinit
      • From: Eric Albert <email@hidden>
References: 
 >Re: 2.1->2.2 created link error: std::__ioinit (From: Eric Albert <email@hidden>)

  • Prev by Date: Private frameworks
  • Next by Date: Re: Building fat Darwin gcc
  • Previous by thread: Re: 2.1->2.2 created link error: std::__ioinit
  • Next by thread: Re: 2.1->2.2 created link error: std::__ioinit
  • Index(es):
    • Date
    • Thread