qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gregory Bayard <gregory.bay...@gmail.com>
Subject Building qpid 0.10 with Boost 1.46.1
Date Fri, 19 Aug 2011 14:16:57 GMT
I can build qpid 0.10 against boost 1.46.1 fine by hacking configure to
remove the -Werror flag everywhere, but I was thinking I am probably doing
something wrong.  The first warning I hit is the following:

boost_1_46_1/boost/range/has_range_iterator.hpp:22: error: extra ';'

Has anyone found a way to fix the warnings coming out of boost?  Or is there
an undocumented option I did not come across hidden in configure to disable
the Werror flag?

Also, I am trying to start clustering with corosync and I have two identical
RHEL 5 boxes with the same build of qpid 0.10 and corosync service is
running fine on both, but one of the boxes joins the cluster fine while the
other always reports the following error even though no other process is
using that port:

./qpidd --module-dir=./ --cluster-name=TEST -p6999
2011-08-19 10:12:34 notice Initializing CPG
2011-08-19 10:12:34 notice cluster(172.21.35.54:14719 PRE_INIT)
configuration change: 172.21.35.54:14719
2011-08-19 10:12:34 notice cluster(172.21.35.54:14719 PRE_INIT) Members
joined: 172.21.35.54:14719
2011-08-19 10:12:34 notice SASL disabled: No Authentication Performed
2011-08-19 10:12:34 notice Listening on TCP port 6999
2011-08-19 10:12:34 critical Unexpected error: Can't bind to port :6999:
Address already in use (qpid/sys/posix/Socket.cpp:201)
Invalid argument

Any ideas on both issues would be greatly appreciated, thanks!

Greg

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message