It looks as though there are two issues here:
a/ My understanding is that upstream does a dlopen() on libdlm_lt.so in
order to be able to use libdlm_lt.so.2 or libdlm_lt.so.3 depending on
the system. On Debian/squeeze or better, the package in use is libdlm3,
so libo2dlm should dlopen()
On Mon, Jun 28, 2010 at 1:02 AM, Jeremy Lainé jeremy.la...@m4x.org wrote:
It looks as though there are two issues here:
a/ My understanding is that upstream does a dlopen() on libdlm_lt.so in
order to be able to use libdlm_lt.so.2 or libdlm_lt.so.3 depending on the
system.
OK, but that will
On Mon, Jun 28, 2010 at 10:02:06AM +0200, Jeremy Lainé wrote:
b/ libdlm3 is only required when using a userspace cluster stack
instead of the built-in o2cb. Therefore, having a ocfs2-tools
*depend* on libdlm3 is probably wrong. I think that making
ocfs2-tools-cman and ocfs2-tools-pacemaker
On Mon, Jun 28, 2010 at 08:13:25AM -0700, Patrick J. LoPresti wrote:
2) Have configure detect the version of libdlm_lt.so.N at compile
time, and have libo2dlm use that.
or
3) Modify libo2dlm/o2dlm.c to attempt to dlopen() libdlm_lt.so.3, then
try libdlm_lt.so.2 if that fails. This is
Package: ocfs2-tools
Version: 1.4.4-2
While trying to run mkfs.ocfs2 (Pacemaker cluster stack), I
consistently got the following error:
Unable to access cluster service while initializing the dlm
I tracked this down to mkfs.ocfs2 attempting to dlopen()
libdlm_lt.so. Unfortunately, this symlink
5 matches
Mail list logo
