RE: loading modules that depends on dylibs on Ubuntu

["Antonio Scuri" <scuri@...>]

 If I'm not wrong dlopen only find secondary dynamic libraries if
LD_LIBRARY_PATH is set accordingly.

 I mean, libmuro.so is only found if its folder is on the LD_LIBRARY_PATH.

Best,
scuri

> -----Original Message-----
> From: lua-bounces@bazar2.conectiva.com.br [mailto:lua-
> bounces@bazar2.conectiva.com.br] On Behalf Of Wesley Smith
> Sent: terça-feira, 20 de janeiro de 2009 00:21
> To: Lua list
> Subject: Re: loading modules that depends on dylibs on Ubuntu
> 
> > Indeed. You didn't mention two .so files in your original post. A
> > better description of your problem might get more specific advice.
> 
> Not to belabor the point, but I did mention it, but perhaps my
> description was convoluted.
> Quote: "the module links against a shared library itself"
> 
> > What do you mean by "loads fine"? It can't be that fine, if it ain't
> working!
> >
> > What happens? How about some lua code, and some console output? gdb
> > stack trace? Something?
> >
> 
> I mean require("muro") find muro.so.  The trouble is in loading
> muro.so, the libmuro.so dependency is not resolved.  All things
> Lua-related in this case are working fine, which is what I meant in my
> previous message.
> 
> 
> > Is lua finding muro.so? If not, your package.cpath needs work.
> 
> Yes.  This is not the problem.
> 
> 
> >
> > dlopen uses ld to resolve references in muro.so.
> good to know.
> 
> > Is ld resolving refs? When you run ldd on muro.so, what does it say?
> > It should say muro.so depends on libmuro.so, and print the full path
> > to libmuro.so. If it doesn't, your ld configuration or cache needs
> > work.
> >
> 
> I'll test these later in the week as I'm no longer on the same
> machine.  I usually work on OSX, and there are some things dealing
> with shared libs on ubuntu that just don't translate.  Thanks for the
> pointers, I'll see what I can find out.
> 
> wes