Building qpid 0.10 with Boost 1.46.1

[Gregory Bayard <gr...@gmail.com>]

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

Re: Building qpid 0.10 with Boost 1.46.1

[Gordon Sim <gs...@redhat.com>]

On 08/19/2011 03:16 PM, Gregory Bayard wrote:
> 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?

Does --enable-warnings=no not do it?

> 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

Do you get the same error whatever port you choose? It sounds like 
perhaps you are loading two modules that are both trying to listen on 
the same port. Do you have anything referring to that port in 
/etc/qpidd.conf?

Perhaps turn up the logging --log-enable trace+ to see if anything there 
sheds further light on the issue?

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org