[ClusterLabs] Pacemaker build error

[Ken Gaillot]

On 11/04/2015 09:31 AM, Ken Gaillot wrote:
> On 11/03/2015 11:10 PM, Jim Van Oosten wrote:
>>
>>
>> I am getting a compile error when building Pacemaker on Linux version
>> 2.6.32-431.el6.x86_64.
>>
>> The build commands:
>>
>> git clone git://github.com/ClusterLabs/pacemaker.git
>> cd pacemaker
>> ./autogen.sh && ./configure --prefix=/usr --sysconfdir=/etc
>> make
>> make install
>>
>> The compile error:
>>
>> Making install in services
>> gmake[2]: Entering directory
>> `/tmp/software/HA_linux/pacemaker/lib/services'
>>   CC       libcrmservice_la-services.lo
>> services.c: In function 'resources_action_create':
>> services.c:153: error: 'svc_action_private_t' has no member named 'pending'
>> services.c: In function 'services_action_create_generic':
>> services.c:340: error: 'svc_action_private_t' has no member named 'pending'
>> gmake[2]: *** [libcrmservice_la-services.lo] Error 1
>> gmake[2]: Leaving directory `/tmp/software/HA_linux/pacemaker/lib/services'
>> gmake[1]: *** [install-recursive] Error 1
>> gmake[1]: Leaving directory `/tmp/software/HA_linux/pacemaker/lib'
>> make: *** [install-recursive] Error 1
>>
>>
>> The pending field that services.c is attenpting to set is conditioned on
>> the SUPPORT_DBUS flag in services_private.h.
>>
>> pacemaker/lib/services/services_private.h
>>
>>                    
>>  #if SUPPORT_DBUS  
>>                    
>>                    
>>                    
>>
>>
>>                         
>>                         
>>                         
>>  DBusPendingCall*       
>>  pending;               
>>                         
>>                         
>>                         
>>                         
>>                         
>>  unsigned timerid;      
>>                         
>>                         
>>                         
>>
>>
>>         
>>  #endif 
>>         
>>
>>
>>
>>
>> Am I building Pacemaker incorrectly or should I open an defect for this
>> problem?
>>
>> Jim VanOosten
>> jimvo at  us.ibm.com
> 
> This report is enough; I'll do up a quick fix today. Thanks for catching it.

The fix is upstream. Pull the latest commit and you should be good to go.