Hi Ganesh,

I have proton 0.11 compiled and examples working.  I am using gcc version 4.1.2 
and I have Python 2.6.8 installed.  

While moving to Centos 7 is in the works is there any other way to get past 
this issue?

There is considerable interest in demonstrating dispatch prior to a "deeper" 
commitment.

Thanks.
________________________________________
From: Ganesh Murthy [[email protected]]
Sent: Thursday, February 11, 2016 8:36 AM
To: [email protected]
Subject: Re: Hekp with Dispatch Build "difficulties"

Hi Paul,
    I tried to get a Docker environment going with CentOS 5 but ran into 
several problems. CentOS 5 is pre-2008 and has an old version of Python. Is 
there a way you can get to a recent version of CentOS (CentOS 7?). If you want 
to stay on CentOS 5, please try using dispatch 0.4 and proton 0.9.

Thanks.

----- Original Message -----
From: "Paul A. Flores" <[email protected]>
To: [email protected]
Sent: Wednesday, February 10, 2016 5:40:18 PM
Subject: Hekp with Dispatch Build "difficulties"

I have been trying to get Dispatch 0.5 to build.



I am seeing the following issue.  Can anyone help me get past this issue?



[ 26%] Building C object src/CMakeFiles/qpid-dispatch.dir/lrp.c.o
cc1: warnings being treated as errors
/home/pflores/shop/qpid-dispatch-0.5/src/lrp.c: In function 
‘qd_lrpc_open_handler’:
/home/pflores/shop/qpid-dispatch-0.5/src/lrp.c:59: warning: dereferencing 
type-punned pointer will break strict-aliasing rules
/home/pflores/shop/qpid-dispatch-0.5/src/lrp.c: In function 
‘qd_lrpc_close_handler’:
/home/pflores/shop/qpid-dispatch-0.5/src/lrp.c:115: warning: dereferencing 
type-punned pointer will break strict-aliasing rules
make[2]: *** [src/CMakeFiles/qpid-dispatch.dir/lrp.c.o] Error 1
make[1]: *** [src/CMakeFiles/qpid-dispatch.dir/all] Error 2
make: *** [all] Error 2

System is Centos 5.11

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

Reply via email to