Ted, It appears to compile but the undefined references. I do have python 2.6 installed on the system but from the linker it appears to be finding an earlier version. I'll look but if you have an idea right off the top of your head how I can get cmake to specifically "look for" python 2.6 that would be appreciated.
Paul ________________________________________ From: Ted Ross [[email protected]] Sent: Thursday, February 11, 2016 11:33 AM To: [email protected] Subject: Re: Help with Dispatch Build "difficulties" Paul, That's odd because that code only has an effect if you are running Python earlier than 2.5. You said you were using 2.6.8. Do you have the right version (2.6.8) of python-devel installed? Aside from that issue, I think everything else was a warning. -Ted On 02/11/2016 12:24 PM, Flores, Paul A. wrote: > Ted, > > FYI inserting the following into python_embedded.c resolved one issue. > > Paul > > #if PY_VERSION_HEX < 0x02050000 && !defined(PY_SSIZE_T_MIN) > typedef int Py_ssize_t; > #define PY_SSIZE_T_MAX INT_MAX > #define PY_SSIZE_T_MIN INT_MIN > #endif > > > ________________________________________ > From: Ted Ross [[email protected]] > Sent: Thursday, February 11, 2016 9:50 AM > To: [email protected] > Subject: Re: Help with Dispatch Build "difficulties" > > Paul, > > Can you run a "make -k" on your Dispatch source to get a more complete > list of build failures? I'd like to have a look at them. > > If you have proton 0.11, then dispatch _should_ build. > > -Ted > > On 02/11/2016 10:14 AM, Flores, Paul A. wrote: >> 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] >> > > --------------------------------------------------------------------- > 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] > --------------------------------------------------------------------- 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]
