[Gluster-devel] glfsheal test failures
Jeff Darcy
jdarcy at redhat.com
Fri Dec 12 13:00:59 UTC 2014
> On Fri, Dec 12, 2014 at 12:18:01AM -0500, Jeff Darcy wrote:
> > As far as I can tell, yes. Those end up in /lib64 where they are found
> > without any special configuration on our part. Translators are different;
> > we
> > install those in a different location that the system doesn't already know
> > about.
>
> That is not the only problem: DSO and libraries are not linked the same way.
What distinction is important here? In my experience - not just on Linux - a
shared library *is* a dynamic shared object unless one specifically links
statically, so the difference isn't the thing itself. Are you saying there's
a difference in how the thing is specified on the linker command line (e.g.
"-lafr" vs. "afr.so")? If using "-l" even for libraries in known locations
is a problem, why hasn't this issue come up e.g. for libglusterfs?
More information about the Gluster-devel
mailing list