[libvirt] Mac OS X: dyld: lazy symbol binding failed

[Mitchell Hashimoto]

I've been working with Justin, and we've been making some progress.
However, I have another question for this list. As a follow-up to
this, I realized that when I download the snapshots and just
"./configure; make; make install" then I get the lazy binding issue.
However, if I go through the entire autogen process:

./autogen.sh
make
make install

Then this issue goes away. Could this be indicative of a bug in the
autotools input perhaps on generating the packages on machines which
aren't Macs? How do I test the packaging myself (on a Mac) so that I
can verify this theory?

Given this information, does this shed some light and perhaps reveal a
problem someone more experienced than I would see?

Thanks,
Mitchell

On Fri, Oct 8, 2010 at 11:38 AM, Mitchell Hashimoto
<mitchell.hashimoto at gmail.com> wrote:
> Hi,
>
> This is a cross-post from libvirt-users since there didn't seem to be
> anyone there familiar with what is going on and this is a dev issue as
> well.
>
> I'm using the Ruby/FFI libvirt library and getting this consistently
> on Mac OS X:
>
> ruby-1.9.2-p0 > FFI::Libvirt.virInitialize
> dyld: lazy symbol binding failed: Symbol not found: _virThreadInitialize
>  Referenced from: /usr/local/lib/libvirt.dylib
>  Expected in: flat namespace
>
> dyld: Symbol not found: _virThreadInitialize
>  Referenced from: /usr/local/lib/libvirt.dylib
>  Expected in: flat namespace
>
> Trace/BPT trap
>
> I exported DYLD_PRINT_LIBRARIES and it shows that libvirt.dylib is
> loaded in the process space, but the above still occurs. When I
> statically link into a C program it works fine, however. Anyone have
> any idea what could be causing this?
>
> See this archive if you'd like to catch up on what was said in
> libvirt-users (its not a long thread):
> https://www.redhat.com/archives/libvirt-users/2010-October/msg00050.html
>
> Thanks,
> Mitchell
>