[Pacemaker] build issues
Please disregard the build issues I asked about. Another clone that I pulled seems to build fine. Sorry about that. -Frank From: Frank DiMeo [mailto:frank.di...@bigbandnet.com] Sent: Monday, December 07, 2009 5:13 PM To: pacemaker@oss.clusterlabs.org Subject: Re: [Pacemaker] patch for rsc_order loops. I pulled a copy of the latest corosync sources, and the mar_gen.h file in that package is identical to the one I have in /usr/include/corosync, so that's not the problem. Is anyone else having problems building the tip of the repo? -Frank From: Frank DiMeo [mailto:frank.di...@bigbandnet.com] Sent: Monday, December 07, 2009 5:03 PM To: pacemaker@oss.clusterlabs.org Subject: Re: [Pacemaker] patch for rsc_order loops. Actually, now that I look at it more closely, that a corosync file. Maybe I need to update my corosync source? -Frank From: Frank DiMeo [mailto:frank.di...@bigbandnet.com] Sent: Monday, December 07, 2009 4:58 PM To: pacemaker@oss.clusterlabs.org Subject: Re: [Pacemaker] patch for rsc_order loops. Is the repo at http://hg.clusterlabs.org/pacemaker/stable-1.0 broken? When I try to build it, I get an error in mar_gen.h, line 181. Expected ')' before '*' token. -Frank From: Frank DiMeo [mailto:frank.di...@bigbandnet.com] Sent: Monday, December 07, 2009 2:19 PM To: Andrew Beekhof Cc: pacemaker@oss.clusterlabs.org Subject: [Pacemaker] patch for rsc_order loops. I've enclosed at mercurial patch for what I believe is a fix for the resource ordering loop creation that I've been chasing. Please look it over and if you approve, I can submit it. -Frank ___ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
[Pacemaker] 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 ega...@broadvox.netmailto:ega...@broadvox.net [cid:image001.gif@01CA587D.C02C5E90] 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. inline: image001.gif___ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Re: [Pacemaker] Pacemaker Build Issues on CentOS 5.3 64-bit
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@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
