• 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: non_lazy_ptr in general
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: non_lazy_ptr in general


  • Subject: Re: non_lazy_ptr in general
  • From: Bob Clark <email@hidden>
  • Date: Thu, 13 Nov 2008 15:55:43 -0800

Hi Nick--

I don't have any answers, but I've been moving projects from Xcode 2.5 to 3.1 and I've been seeing a lot of these non_lazy_ptr link errors too.

I'm seeing them mostly when I'm trying to link to some in-house frameworks (that I've also recently converted from Xcode 2.5 to 3.1). I've been getting frustrated trying to figure out just what has changed between Xcode 2.5 and Xcode 3.1 that's making it pickier about linking.

(Is this consistent with what you're seeing -- earlier versions of Xcode work fine, while later versions such as 3.x are failing?)

--Bob

On Nov 12, 2008, at 6:13 PM, Nick Zitzmann wrote:

Yesterday, I was building some open source code that depended on a third-party library, liboil. Liboil is a library that defines most of its symbols as generic pointers, then provides architecture- specific implementations of each function, and these implementations are assigned to the memory addresses of those pointers at initialization time. I'm guessing they did this so they could support a very broad number of architectures and CPU features.

The problem is, when linking it against the project that was using it, I got a linker error like this:

Undefined symbols:
"_some_function", referenced from:
    _some_function$non_lazy_ptr in some_source.o

So I searched Google for non_lazy_ptr, and saw lots of other people who have had this problem compiling various projects out there on Mac OS X, and no one really knew what was causing this to happen, or how to fix it.

So what causes these non_lazy_ptr linker errors, and how do I properly fix them? My interim solution was to use the -U linker option to make the linker dynamically look up the symbol, but I suspect that wasn't the correct solution...

Nick Zitzmann
<http://seiryu.home.comcast.net/>

_______________________________________________ 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: non_lazy_ptr in general
      • From: Nick Zitzmann <email@hidden>
References: 
 >non_lazy_ptr in general (From: Nick Zitzmann <email@hidden>)

  • Prev by Date: Re: Determining which processes are utilizing the disk?
  • Next by Date: Merge C++ library and Objective-C
  • Previous by thread: Re: non_lazy_ptr in general
  • Next by thread: Re: non_lazy_ptr in general
  • Index(es):
    • Date
    • Thread