Hello Vladislav,
El 31/10/12 12:35, Vladislav Bogdanov escribió:
> 31.10.2012 12:39, Bernardo Cabezas Serra wrote:
>>
>> El 30/10/12 17:29, Bernardo Cabezas Serra escribió:
> Are you sure you have "clean" corosync installation and no bits from 1.x
> version remain installed?
Yesss, that was de pr
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, COR
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
Hello,
Got some errors compiling pacemaker 1.1.8 (also tested previous
versions) on top of corosync 2.1.0.
At the end of the mail you can se ./configure output for both corosync
and pacemaker. [**]
First error (solved for me), was this one:
make[2]: Entering directory `/usr/src/pacemaker.git/lib