Hi, I am building Qpid 0.3 under CentOS 6.6 and get these output:
cc1plus: warnings being treated as errors
/root/qpid-cpp-0.30/src/../include/qpid/framing/DeliveryProperties.h: In member
function ‘bool qpid::client::LocalQueueImpl::get(qpid::client::Message&,
qpid::sys::Duration)’:
/root/qpid-
We've been working on improving the AMQP 1.0 support in ActiveMQ and
I've found that the trunk code for QPid JMS client contains some fixes
that would be nice to have in for testing the fixes that are in the
pipeline for the broker. Was wondering if there is any idea on when the
0.32 release p
On Sat, 2014-11-29 at 17:12 +, Fraser Adams wrote:
> ...
>File "/usr/local/lib/proton/bindings/python/proton.py", line 3209, in
> SASL
> STATE_CONF = PN_SASL_CONF
> NameError: name 'PN_SASL_CONF' is not defined
>
> Can anyone suggest what I'm doing wrong?
Just do a make clean befor
On Fri, Nov 21, 2014 at 05:29:33PM -0700, smartdog wrote:
> What is the alternative to get the qpid-tools?
>
> http://www.ubuntuupdates.org/package/core/trusty/universe/base/qpid-tools
Hi, I'm not entirely sure why the base Ubuntu 14 package set would not
have qpid-tools. However, we do have Qpid
On Sun, Nov 30, 2014 at 04:31:20PM +, Fraser Adams wrote:
> I've been tearing my hair out a bit trying to figure why I can't see the
> relevant Python modules.
>
> I build Proton on a clean Linux Mint 17 system (which is based on Ubuntu
> 14.04)
>
> make all builds successfully and sudo make
On 12/01/2014 01:05 AM, 163邮箱 wrote:
It seems that Ruby is used to generate something related to AMQP. Can I build
Qpid without it and still have AMQP support in client API?
It's possible I'm wrong, but unfortunately I don't think you can build
at all without ruby any more. In the older autot
