[Pacemaker] Errors compiling pacemaker 1.1.8 with corosync 2.1.0

Vladislav Bogdanov bubble at hoster-ok.com
Wed Oct 31 07:35:59 EDT 2012


31.10.2012 12:39, Bernardo Cabezas Serra wrote:
> 
> El 30/10/12 17:29, Bernardo Cabezas Serra escribió:
>> Hello,
>>
>> Got some errors compiling pacemaker 1.1.8 (also tested previous
>> versions) on top of corosync 2.1.0.
> 
> Also tested with corosync 2.0.2, and fails the same.
> 
> In fact, COROSYNC_SOCKET_NAME was removed from corosync a year ago, in
> this changeset:
> https://github.com/corosync/corosync/commit/c6895faa05f2c543a996ed1b08f5bec1b79960ca
> 
> so don't understant how it compiles for someone, because
> lib/cluster/legacy.c uses it.
> Maybe some configure parameter?

Are you sure you have "clean" corosync installation and no bits from 1.x
version remain installed?

legacy.o is not built if SUPPORT_PLUGIN is zero.
lib/cluster/Makefile.am:

if BUILD_CS_SUPPORT
if BUILD_CS_PLUGIN
libcrmcluster_la_SOURCES += legacy.c
else
libcrmcluster_la_SOURCES += corosync.c
endif
endif

And that var set to 1 only if you have libconfdb installed. corosync2
does not have that library. Look at configure.ac.

Vladislav





More information about the Pacemaker mailing list