[Pacemaker] pacemaker 1.0.3 compilation problem on Fedora 8

[Infos E-Blokos]

----- Original Message ----- 
From: "Andrew Beekhof" <beekhof at gmail.com>
To: <pacemaker at clusterlabs.org>
Sent: Thursday, April 16, 2009 4:11 AM
Subject: Re: [Pacemaker] pacemaker 1.0.3 compilation problem on Fedora 8


> On Thu, Apr 16, 2009 at 09:29, Infos E-Blokos <infos at e-blokos.com> wrote:
>>
>> ----- Original Message ----- From: "Andrew Beekhof" <beekhof at gmail.com>
>> To: <pacemaker at clusterlabs.org>
>> Sent: Thursday, April 16, 2009 3:22 AM
>> Subject: Re: [Pacemaker] pacemaker 1.0.3 compilation problem on Fedora 8
>>
>>
>>> On Thu, Apr 16, 2009 at 09:14, Infos E-Blokos <infos at e-blokos.com> 
>>> wrote:
>>>>
>>>> ----- Original Message ----- From: "Andrew Beekhof" <beekhof at gmail.com>
>>>> To: <pacemaker at clusterlabs.org>
>>>> Sent: Thursday, April 16, 2009 3:05 AM
>>>> Subject: Re: [Pacemaker] pacemaker 1.0.3 compilation problem on Fedora 
>>>> 8
>>>>
>>>>
>>>>> On Thu, Apr 16, 2009 at 07:30, Infos E-Blokos <infos at e-blokos.com>
>>>>> wrote:
>>>>>>
>>>>>> ok, but as Fedora 8 is not updated anymore...
>>>>>> what the solution ?
>>>>>
>>>>> Re-configure with the --disable-fatal-warnings option
>>>>> Or, change the relevant libxml2 header yourself
>>>>
>>>>
>>>> I used the --disable option.. anyway
>>>> cluster-3.0.1rc1 doesn't compile with pacemaker..
>>>
>>> cluster3?
>>> you mean corosync right?
>>> I'm not surprised, their APIs are changing every few days at the
>>> moment which makes it impossible to keep up.
>>
>>
>> yes cluster3... :(
>> ok, I restart from the beginning again.
>> I wish to build a GFS2/openais/pacemaker cluster system on Fedora 8 and 
>> 10.
>> Any suggestions ?
>
> Wait a month.
> I'm told thats when the API will finally stop changing (at which point
> it will be worth fixing pacemaker to build against it).

I'd like to wait, but after a research project of 3 years I want to finish 
this month
to rest a little ;)
anyway, for now I choose another solution and I'll wait

Thanks

Franck



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.