qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Flores, Paul A." <PAUL.A.FLO...@SAIC.COM>
Subject RE: Help with Dispatch Build "difficulties" - new issue
Date Wed, 24 Feb 2016 17:09:05 GMT
Update:

I did as Ken suggested and got a clean build.

But when I go to run "ctest -W" I have a large number of test failing with the error "No module
named proton" appearing in the LastTest.log.

Any help/hints how to resolve this issue?

Thanks.

Paul

________________________________________
From: Ken Giusti [kgiusti@redhat.com]
Sent: Friday, February 12, 2016 9:58 AM
To: users@qpid.apache.org
Subject: Re: Help with Dispatch Build "difficulties"

Hi Paul,

I spun up a stock Centos5 VM, and got qpid-dispatch to build and install.

Here's roughly what I did:

First, I did a "yum install python26 python26-devel"

These packages are available from the epel repo.  Use these.

Then I pulled down qpid-proton-0.11.1.tar.gz and qpid-dispatch-0.5.tar.gz from qpid.apache.org.

Unpacked, built and installed qpid-proton-0.11.1.  I did tweak the config a bit via ccmake:
 I turned "OFF" all the extra build stuff, specifically:

BUILD_CPP=OFF
BUILD_GO=OFF
...
BUILD_TESTING=OFF

And I verified that ccmake shows the correct python26 libraries/includes before running "make
install".

Then I unpacked qpid-dispatch, modified the CMakeLists.txt file to remove the "-Werror" flag,
and built/installed.

No errors occurred!

But when I ran qpid-dispatch, I had to set the PYTHONPATH and LD_LIBRARY_PATH to find the
locally-installed libraries:

LD_LIBRARY_PATH=/usr/local/lib PYTHONPATH=/usr/local/lib/python2.6/site-packages /usr/local/sbin/qdrouterd

Be careful: my VM is i686 - you'll probably have to change the paths above to lib64...


----- Original Message -----
> From: "Paul A. Flores" <PAUL.A.FLORES@SAIC.COM>
> To: users@qpid.apache.org
> Sent: Thursday, February 11, 2016 4:48:15 PM
> Subject: RE: Help with Dispatch Build "difficulties"
>
> Ken,
>
> It didn't work and errors out much earlier.
>
> Paul
>
> ________________________________________
> From: Ken Giusti [kgiusti@redhat.com]
> Sent: Thursday, February 11, 2016 3:16 PM
> To: users@qpid.apache.org
> Subject: Re: Help with Dispatch Build "difficulties"
>
> Hey - it seems like the math library is not being linked in.  Apparently it's
> required by that version of python, and cmake can't figure that out.
>
> A workaround: try adding the library to the cmake file in src/CMakeLists.txt.
>
> You'll want to change:
>
> target_link_libraries(qpid-dispatch ${Proton_LIBRARIES} ${pthread_lib}
> ${rt_lib} ${dl_lib} ${PYTHON_LIBRARIES})
>
> To:
>
> target_link_libraries(qpid-dispatch ${Proton_LIBRARIES} ${pthread_lib}
> ${rt_lib} ${dl_lib} ${PYTHON_LIBRARIES} m)
>
> Totally untested - I don't have access to a centos5 box atm.  I'm assuming
> libm.so is available on your system.
>
> Then remove the CMakeCache.txt file in your build directory, and re-run
> cmake.  Don't forget to change the python settings before building.
>
> I wouldn't try python 3.3 at this point, IMHO.
>
>
> ----- Original Message -----
> > From: "Paul A. Flores" <PAUL.A.FLORES@SAIC.COM>
> > To: users@qpid.apache.org
> > Sent: Thursday, February 11, 2016 3:51:58 PM
> > Subject: RE: Help with Dispatch Build "difficulties"
> >
> > Ken,
> >
> > I installed Python 2.7 in my Centos 5 environment using some nifty
> > instructions that I found on
> > http://toomuchdata.com/2014/02/16/how-to-install-python-on-centos/.  This
> > reduced the errors to the following.
> >
> > Should I try a Python 3.3 installation?
> >
> > Paul
> >
> > /sbin/Python-2.7.6/libpython2.7.a(floatobject.o): In function
> > `float_is_integer':
> > /sbin/Python-2.7.6/Objects/floatobject.c:986: undefined reference to
> > `floor'
> > /sbin/Python-2.7.6/libpython2.7.a(floatobject.o): In function
> > `_Py_double_round':
> > /sbin/Python-2.7.6/Objects/floatobject.c:1093: undefined reference to
> > `round'
> > /sbin/Python-2.7.6/Objects/floatobject.c:1132: undefined reference to
> > `floor'
> > /sbin/Python-2.7.6/Objects/floatobject.c:1146: undefined reference to
> > `fmod'
> > /sbin/Python-2.7.6/libpython2.7.a(floatobject.o): In function
> > `float_as_integer_ratio':
> > /sbin/Python-2.7.6/Objects/floatobject.c:1738: undefined reference to
> > `floor'
> > /sbin/Python-2.7.6/libpython2.7.a(floatobject.o): In function `float_pow':
> > /sbin/Python-2.7.6/Objects/floatobject.c:853: undefined reference to `fmod'
> > /sbin/Python-2.7.6/Objects/floatobject.c:863: undefined reference to `fmod'
> > /sbin/Python-2.7.6/Objects/floatobject.c:912: undefined reference to `pow'
> > /sbin/Python-2.7.6/Objects/floatobject.c:878: undefined reference to
> > `floor'
> > /sbin/Python-2.7.6/Objects/floatobject.c:888: undefined reference to `fmod'
> > /sbin/Python-2.7.6/libpython2.7.a(floatobject.o): In function
> > `float_divmod':
> > /sbin/Python-2.7.6/Objects/floatobject.c:750: undefined reference to `fmod'
> > /sbin/Python-2.7.6/Objects/floatobject.c:776: undefined reference to
> > `floor'
> > /sbin/Python-2.7.6/libpython2.7.a(floatobject.o): In function `float_rem':
> > /sbin/Python-2.7.6/Objects/floatobject.c:718: undefined reference to `fmod'
> > /sbin/Python-2.7.6/libpython2.7.a(longobject.o): In function
> > `PyLong_FromString':
> > /sbin/Python-2.7.6/Objects/longobject.c:1869: undefined reference to `log'
> > /sbin/Python-2.7.6/Objects/longobject.c:1869: undefined reference to `log'
> > /sbin/Python-2.7.6/libpython2.7.a(signalmodule.o): In function
> > `timeval_from_double':
> > /sbin/Python-2.7.6/./Modules/signalmodule.c:112: undefined reference to
> > `floor'
> > /sbin/Python-2.7.6/./Modules/signalmodule.c:113: undefined reference to
> > `fmod'
> > /sbin/Python-2.7.6/./Modules/signalmodule.c:112: undefined reference to
> > `floor'
> > /sbin/Python-2.7.6/./Modules/signalmodule.c:113: undefined reference to
> > `fmod'
> > /sbin/Python-2.7.6/libpython2.7.a(posixmodule.o): In function
> > `posix_forkpty':
> > /sbin/Python-2.7.6/./Modules/posixmodule.c:3958: undefined reference to
> > `forkpty'
> > /sbin/Python-2.7.6/libpython2.7.a(posixmodule.o): In function
> > `posix_openpty':
> > /sbin/Python-2.7.6/./Modules/posixmodule.c:3898: undefined reference to
> > `openpty'
> > /sbin/Python-2.7.6/libpython2.7.a(complexobject.o): In function
> > `_Py_c_abs':
> > /sbin/Python-2.7.6/Objects/complexobject.c:210: undefined reference to
> > `hypot'
> > /sbin/Python-2.7.6/libpython2.7.a(complexobject.o): In function
> > `_Py_c_pow':
> > /sbin/Python-2.7.6/Objects/complexobject.c:139: undefined reference to
> > `hypot'
> > /sbin/Python-2.7.6/Objects/complexobject.c:140: undefined reference to
> > `pow'
> > /sbin/Python-2.7.6/Objects/complexobject.c:141: undefined reference to
> > `atan2'
> > /sbin/Python-2.7.6/Objects/complexobject.c:147: undefined reference to
> > `cos'
> > /sbin/Python-2.7.6/Objects/complexobject.c:148: undefined reference to
> > `sin'
> > /sbin/Python-2.7.6/Objects/complexobject.c:144: undefined reference to
> > `exp'
> > /sbin/Python-2.7.6/Objects/complexobject.c:145: undefined reference to
> > `log'
> > /sbin/Python-2.7.6/libpython2.7.a(complexobject.o): In function
> > `complex_divmod':
> > /sbin/Python-2.7.6/Objects/complexobject.c:638: undefined reference to
> > `floor'
> > /sbin/Python-2.7.6/libpython2.7.a(complexobject.o): In function
> > `complex_remainder':
> > /sbin/Python-2.7.6/Objects/complexobject.c:612: undefined reference to
> > `floor'
> > collect2: ld returned 1 exit status
> > make[2]: *** [src/libqpid-dispatch.so.1.0] Error 1
> > make[2]: Target `src/CMakeFiles/qpid-dispatch.dir/build' not remade because
> > of errors.
> > make[1]: *** [src/CMakeFiles/qpid-dispatch.dir/all] Error 2
> > make[1]: Target `all' not remade because of errors.
> > make: *** [all] Error 2
> > make: Target `default_target' not remade because of errors.
> >
> >
> > ________________________________________
> > From: Ken Giusti [kgiusti@redhat.com]
> > Sent: Thursday, February 11, 2016 12:27 PM
> > To: users@qpid.apache.org
> > Subject: Re: Help with Dispatch Build "difficulties"
> >
> > Paul,
> >
> > You can use 'ccmake' to edit the paths used to find your python install.
> >
> > Run ccmake .. from your build directory, it will display all the
> > configuration name and settings.  Type 't' to toggle to advance mode.  use
> > the up/down arrows to find
> >
> > PYTHON_LIBRARY
> > PYTHON_INCLUDE_DIR
> > PYTHON_EXECUTABLE
> >
> > You can edit each value to set it to the proper files.  Then hit 'c' to
> > configure and then 'g' to generate.
> >
> > The re-run make install.
> >
> > You can also set them whenever you run the cmake command:
> >
> > cmake -DPYTHON_LIBRARY=<blah> ....
> >
> >
> > ----- Original Message -----
> > > From: "Paul A. Flores" <PAUL.A.FLORES@SAIC.COM>
> > > To: users@qpid.apache.org
> > > Sent: Thursday, February 11, 2016 1:07:29 PM
> > > Subject: RE: Help with Dispatch Build "difficulties"
> > >
> > > 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 [tross@redhat.com]
> > > Sent: Thursday, February 11, 2016 11:33 AM
> > > To: users@qpid.apache.org
> > > 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 [tross@redhat.com]
> > > > Sent: Thursday, February 11, 2016 9:50 AM
> > > > To: users@qpid.apache.org
> > > > 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 [gmurthy@redhat.com]
> > > >> Sent: Thursday, February 11, 2016 8:36 AM
> > > >> To: users@qpid.apache.org
> > > >> 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" <PAUL.A.FLORES@SAIC.COM>
> > > >> To: users@qpid.apache.org
> > > >> 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: users-unsubscribe@qpid.apache.org
> > > >> For additional commands, e-mail: users-help@qpid.apache.org
> > > >> ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > >> For additional commands, e-mail: users-help@qpid.apache.org
> > > >>
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > > For additional commands, e-mail: users-help@qpid.apache.org
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > > For additional commands, e-mail: users-help@qpid.apache.org
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > For additional commands, e-mail: users-help@qpid.apache.org
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > For additional commands, e-mail: users-help@qpid.apache.org
> > >
> > >
> >
> > --
> > -K
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > For additional commands, e-mail: users-help@qpid.apache.org
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > For additional commands, e-mail: users-help@qpid.apache.org
> >
> >
>
> --
> -K
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>

--
-K

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Mime
View raw message