Christian Fromme wrote
> Hi,
> 
> On Tue, May 21, 2013 at 12:54 PM, pela <

> mpela.gatti@

> > wrote:
> 
>> I'm trying to build qpid c++ from 0.20 source distribution but I get the
>> following error:
>>
>> In file included from
>> /home/users/mpelagatti/qpid/qpidc-0.20/src/qpid/UrlArray.cpp:23:
>> /home/users/mpelagatti/qpid/qpidc-0.20/src/../include/qpid/framing/FieldValue.h:193:
>> error: got 2 template parameters for `T
>> qpid::framing::FieldValue::getIntegerValue() const'
>> /home/users/mpelagatti/qpid/qpidc-0.20/src/../include/qpid/framing/FieldValue.h:193:
>> error:   but 1 required
>> /home/users/mpelagatti/qpid/qpidc-0.20/src/../include/qpid/framing/FieldValue.h:210:
>> error: redefinition of `T qpid::framing::FieldValue::getIntegerValue()
>> const'
>> /home/users/mpelagatti/qpid/qpidc-0.20/src/../include/qpid/framing/FieldValue.h:193:
>> error: `T qpid::framing::FieldValue::getIntegerValue() const' previously
>> declared here
>> make[2]: *** [src/CMakeFiles/qpidcommon.dir/qpid/UrlArray.o] Error 1
>> make[1]: *** [src/CMakeFiles/qpidcommon.dir/all] Error 2
> 
> I can build 0.20 fine on a SLES11 system using configure/make. It
> doesn't look like this would help in your case, but I had to run gcc
> with "--disable-warnings".
> 
> Best,
> Christian
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: 

> [email protected]

> For additional commands, e-mail: 

> [email protected]


I'm on CentOS 5.5 and get the same error using configure/make or cmake. The
error doesn't seem caused by missing pre-requisites though, more like a c++
error. Actually I realize this is raised by gcc 3.4 but not gcc-4.4. Maybe
support for gcc 3.4 has been dropped?

Thanks
Marco



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/c-Error-while-building-qpid-0-20-from-source-distribution-tp7593162p7593168.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to