• 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
gcc vs. stdc++ dylib usage
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

gcc vs. stdc++ dylib usage


  • Subject: gcc vs. stdc++ dylib usage
  • From: "smack supersonic" <email@hidden>
  • Date: Mon, 17 Apr 2006 05:06:11 +0000

Hi,

I have noticed that when building with XCode and/or directly via command line the following two dylib's are linked with my binary:

/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.4.0)
/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0)


Although everything works just fine, i am little bit worried that two almost identical dll's are used!?

So my question is:

Is there a way to force either of this dll's to be mutualy exclusive?

Shouldnt this cause problems if in more complex example (host with plug-in components) is dynamically loading plug-in modules that may use either of these libraries?

Thanks,

mj


_______________________________________________ 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: gcc vs. stdc++ dylib usage
      • From: Chris Espinosa <email@hidden>
    • Re: gcc vs. stdc++ dylib usage
      • From: Eric Albert <email@hidden>
  • Prev by Date: gcc 4.0, a framework, and dynamic_cast problems
  • Next by Date: Re: gcc vs. stdc++ dylib usage
  • Previous by thread: Re: gcc 4.0, a framework, and dynamic_cast problems
  • Next by thread: Re: gcc vs. stdc++ dylib usage
  • Index(es):
    • Date
    • Thread