Which Qpid version, and which OS is this on?

> -----Original Message-----
> From: ricardlf [mailto:[email protected]] 
> Sent: Thursday, June 18, 2009 10:42 AM
> To: [email protected]
> Subject: Problem building Qpid C++ broker
> 
> 
> 
> Hi, I'm trying to install Qpid C++ broker but when I try to 
> "make all" I'm
> getting the following errors:
> 
> In function 'void* memset(void*, int, size_t)',
>     inlined from 
> 'qpid::cluster::Cpg::Cpg(qpid::cluster::Cpg::Handler&)' at
> qpid/cluster/Cpg.cpp:75:
> /usr/include/bits/string3.h:82: error: call to 
> '__warn_memset_zero_len'
> declared with attribute warning: memset used with constant zero
length
> parameter; this could be due to transposed parameters
> In function 'void* memset(void*, int, size_t)',
>     inlined from 
> 'qpid::cluster::Cpg::Cpg(qpid::cluster::Cpg::Handler&)' at
> qpid/cluster/Cpg.cpp:75:
> /usr/include/bits/string3.h:82: error: call to 
> '__warn_memset_zero_len'
> declared with attribute warning: memset used with constant zero
length
> parameter; this could be due to transposed parameters
> make[3]: *** [qpid/cluster/Cpg.lo] Error 1
> make[3]: se sale del directorio `/home/ricard/tempDir/qpidc-0.5/src'
> make[2]: *** [all-recursive] Error 1
> make[2]: se sale del directorio `/home/ricard/tempDir/qpidc-0.5/src'
> make[1]: *** [all] Error 2
> make[1]: se sale del directorio `/home/ricard/tempDir/qpidc-0.5/src'
> make: *** [all-recursive] Error 1
> 
> Could anyone help me?
> Thank you very much.
> -- 
> View this message in context: 
> http://n2.nabble.com/Problem-building-Qpid-C%2B%2B-broker-tp31
13713p3113713.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[email protected]



---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[email protected]

Reply via email to