Dejan, I do not know if it is related, but I am getting problem now to compile Corosync. Strangely I did the same on the first machine, so it might be another package in x86 but I bet in something with autoconf And pkg-config.
Could you put a light on this? ./configure: line 6603: syntax error near unexpected token `corosync,corosync'./configure: line 6603: `PKG_CHECK_MODULES(corosync,corosync)' pkg-config - 0.25autoconf (GNU Autoconf) 2.66m4 (GNU M4) 1.4.15 I got loads of warnings with autoconf 2.68, then I downgrade and no errors are generated by autogen. Thank you once again. > Date: Mon, 13 Aug 2012 18:07:14 +0200 > From: [email protected] > To: [email protected] > Subject: Re: [Linux-HA] Cluster glue IPCSocket error > > On Mon, Aug 13, 2012 at 03:01:27PM +0000, Heitor Lessa wrote: > > Exactly Dejan. > > Unfortunately this happen only with pacemaker repo, but if you have a look > > at the output of uname command everything is ok: > > Linux ha_web1 2.6.18-308.8.2.el5xen #1 SMP Tue Jun 12 10:39:28 EDT 2012 > > x86_64 x86_64 x86_64 GNU/Linux > > I was having a look at make output and figure out that possibly there were > > another lib in i386 overriding one in x86_64. Then looking at my procedure > > I have been creating I found out that glib2-devel was installed using > > normally without specifying its arch, which got me a big problem with > > e2fsprogs-devel (needed also for cluster stack). > > > > I think it might help another ones, but apart from Development Tools group > > I had to install these ones: > > glib2-devel.x86_64libxml2-devel.x86_64libaio-devel.x86_64bzip2-devel.x86_64e2fsprogs-devel.x8_64libxslt.x86_64 > > Also upgrade automake And autoconf. > > OK. Actually, I got some reports/subject lines mixed :) > But thanks for reporting back what was the issue. > > Dejan > > > > Date: Mon, 13 Aug 2012 16:36:19 +0200 > > > From: [email protected] > > > To: [email protected] > > > Subject: Re: [Linux-HA] Cluster glue IPCSocket error > > > > > > Hi, > > > > > > On Mon, Aug 13, 2012 at 02:10:59PM +0000, Heitor Lessa wrote: > > > > Thanks Dejan ! > > > > > > > > To solve the problem just issued: > > > > # yum remove glib2-devel# yum install glib2-devel.x86_64 -y > > > > CentOS 5.8 > > > > > > That's quite unexpected. Just out of curiosity: how did you > > > figure that out? Anyway, doesn't yum know which architecture are > > > you running? > > > > > > Thanks, > > > > > > Dejan > > > > > > > > Date: Wed, 8 Aug 2012 14:53:12 +0200 > > > > > From: [email protected] > > > > > To: [email protected] > > > > > Subject: Re: [Linux-HA] Cluster glue IPCSocket error > > > > > > > > > > Hi, > > > > > > > > > > On Fri, Jul 27, 2012 at 12:06:05PM +0000, Heitor Lessa wrote: > > > > > > > > > > > > Hi, > > > > > > I was creating a documentation regarding dependencies and > > > > > > everything that must be done before start to install cluster stack > > > > > > from source, but even yesterday following same steps went ok, today > > > > > > using same CentOS version (5.8) patches did not work as expected. > > > > > > I got stuck in IPC socket error and could not figure out what is > > > > > > happening, also tried older and latest code but with no success. > > > > > > Can someone please put some light here? > > > > > > # make > > > > > > [...]ipcsocket.c: In function 'verify_creds':ipcsocket.c:2257: > > > > > > warning: cast to pointer from integer of different > > > > > > sizeipcsocket.c:2261: warning: cast to pointer from integer of > > > > > > different sizegmake[2]: *** [ipcsocket.lo] Error 1gmake[2]: Leaving > > > > > > directory > > > > > > `/root/cluster_stack/Reusable-Cluster-Components-glue--18489f275f75/lib/clplumbing'gmake[1]: > > > > > > *** [install-recursive] Error 1gmake[1]: Leaving directory > > > > > > `/root/cluster_stack/Reusable-Cluster-Components-glue--18489f275f75/lib'make: > > > > > > *** [install-recursive] Error 1 > > > > > > > > > > > > automake (GNU automake) 1.12libtool (GNU libtool) 2.4.2autoconf > > > > > > (GNU Autoconf) 2.65m4 (GNU M4) 1.4.16pkg-config > > > > > > 0.26glib2.12libaio-0.3 > > > > > > Thanks in advance. > > > > > > > > > > This already came up before. Take a look here: > > > > > > > > > > http://lists.linux-ha.org/pipermail/linux-ha/2007-September/027621.html > > > > > > > > > > Thanks, > > > > > > > > > > Dejan > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Linux-HA mailing list > > > > > > [email protected] > > > > > > http://lists.linux-ha.org/mailman/listinfo/linux-ha > > > > > > See also: http://linux-ha.org/ReportingProblems > > > > > _______________________________________________ > > > > > Linux-HA mailing list > > > > > [email protected] > > > > > http://lists.linux-ha.org/mailman/listinfo/linux-ha > > > > > See also: http://linux-ha.org/ReportingProblems > > > > > > > > _______________________________________________ > > > > Linux-HA mailing list > > > > [email protected] > > > > http://lists.linux-ha.org/mailman/listinfo/linux-ha > > > > See also: http://linux-ha.org/ReportingProblems > > > _______________________________________________ > > > Linux-HA mailing list > > > [email protected] > > > http://lists.linux-ha.org/mailman/listinfo/linux-ha > > > See also: http://linux-ha.org/ReportingProblems > > > > _______________________________________________ > > Linux-HA mailing list > > [email protected] > > http://lists.linux-ha.org/mailman/listinfo/linux-ha > > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
