Mailing List Archive: Linux-HA: Pacemaker

Pacemaker Build Issues on CentOS 5.3 64-bit

Index | Next | Previous | View Threaded

egable at broadvox

Oct 29, 2009, 7:00 AM

Post #1 of 3 (409 views)
Permalink

Pacemaker Build Issues on CentOS 5.3 64-bit

When building Pacemaker (1-0-78e8ab00359a) on CentOS 5.3 64-bit, I run into all sorts of errors. First, the compiler flag '-Werror' is enabled. On CentOS 5.3, gcc issues a warning when you drop a const qualifier on a pointer, which Pacemaker code seems to do all over the place (why does it do that, btw? It breaks good coding practices); so gcc terminates compilation of Pacemaker when encountering these issues.

Once I modify configure.ac to remove this flag and regenerate everything, I run into linking errors because the Makefile LIBS= line tells Pacemaker to use /usr/lib and /lib64 instead of /usr/lib64 and /lib64. I tried to fix this in configure.ac, but I'm not really an expert when it comes to manipulating configure.ac files, so I couldn't get it to work. Instead, I find myself manually modifying nearly every Makefile that gets generated to make it use /usr/lib64 instead of /usr/lib.

If someone could fix these issues quickly, it would save everyone using CentOS lots of time and headache trying to make this work. :) I would be more than happy to test any modifications for anyone willing to try to fix it.

Eliot Gable
Senior Engineer
1228 Euclid Ave, Suite 390
Cleveland, OH 44115

Direct: 216-373-4808
Fax: 216-373-4657
egable [at] broadvox<mailto:egable [at] broadvox>

[cid:image001.gif [at] 01CA587D]
CONFIDENTIAL COMMUNICATION. This e-mail and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to whom it is addressed. If you are not the intended recipient, please call me immediately. BROADVOX is a registered trademark of Broadvox, LLC.

________________________________
CONFIDENTIAL. This e-mail and any attached files are confidential and should be destroyed and/or returned if you are not the intended and proper recipient.

Attachments:

image001.gif (2.25 KB)

Johan.Verrept at able

Oct 29, 2009, 7:17 AM

Post #2 of 3 (384 views)
Permalink

Re: Pacemaker Build Issues on CentOS 5.3 64-bit [In reply to]

On Thu, 2009-10-29 at 10:00 -0400, Eliot Gable wrote:

> Once I modify configure.ac to remove this flag and regenerate
> everything,

you could have used:

./configure --disable-fatal-warnings

> I run into linking errors because the Makefile LIBS= line tells
> Pacemaker to use /usr/lib and /lib64 instead of /usr/lib64 and /lib64.
> I tried to fix this in configure.ac, but I¢m not really an expert when
> it comes to manipulating configure.ac files, so I couldn¢t get it to
> work. Instead, I find myself manually modifying nearly every Makefile
> that gets generated to make it use /usr/lib64 instead of /usr/lib.

have you tried:

./configure --libdir=/usr/lib64

or

./configure LDFLAGS=-L/usr/lib64

J.

_______________________________________________
Pacemaker mailing list
Pacemaker [at] oss
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

andrew at beekhof

Nov 5, 2009, 3:47 AM

Post #3 of 3 (362 views)
Permalink

Re: Pacemaker Build Issues on CentOS 5.3 64-bit [In reply to]

On Thu, Oct 29, 2009 at 3:00 PM, Eliot Gable <egable [at] broadvox> wrote:

> When building Pacemaker (1-0-78e8ab00359a) on CentOS 5.3 64-bit, I run
> into all sorts of errors. First, the compiler flag ‘-Werror’ is enabled. On
> CentOS 5.3, gcc issues a warning when you drop a const qualifier on a
> pointer, which Pacemaker code seems to do all over the place (why does it do
> that, btw? It breaks good coding practices);
>

It doesn't.
There are two (maybe three) places that I know do this and -Wcast-qual is
removed from the CFLAGS used for those files.

> so gcc terminates compilation of Pacemaker when encountering these issues.
>

I just compiled against EPEL-5 and the failure I get is

DEBUG: xml.c: In function 'string2xml':
DEBUG: xml.c:490: warning: argument 2 of 'xmlSetGenericErrorFunc' might be a
candidate for a format attribute
DEBUG: xml.c: In function 'filename2xml':
DEBUG: xml.c:626: warning: argument 2 of 'xmlSetGenericErrorFunc' might be a
candidate for a format attribute

Which is coming from -Wmissing-format-attribute - stupid option which I've
now disabled.
Once I did that, it built just fine with -Werror

> Once I modify configure.ac to remove this flag and regenerate everything,
> I run into linking errors because the Makefile LIBS= line tells Pacemaker to
> use /usr/lib and /lib64 instead of /usr/lib64 and /lib64.
>

Possibly something from your machine?
It builds fine in a clean chroot.

> I tried to fix this in configure.ac, but I’m not really an expert when it
> comes to manipulating configure.ac files, so I couldn’t get it to work.
> Instead, I find myself manually modifying nearly every Makefile that gets
> generated to make it use /usr/lib64 instead of /usr/lib.
>
>
>
> If someone could fix these issues quickly, it would save everyone using
> CentOS lots of time and headache trying to make this work. J I would be
> more than happy to test any modifications for anyone willing to try to fix
> it.
>

You could also use the packages from:
http://clusterlabs.org/rpm/epel-5/

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads