From: Dmitry M. <am...@am...> - 2007-01-31 11:22:11
|
Hi! I'm maintaining FreeBSD port of py-ode. There are no problems when building it with gcc 3.4, but when I try to use gcc 4.1 (which will be introduced in new FreeBSD versions) instead, I get the following errors: Any clues on how this can be fixed? --- cut --- ode_trimesh.c is up to date ode_notrimesh.c is up to date Installing without trimesh support. running build running build_py running build_ext building 'ode' extension gcc41 -fno-strict-aliasing -DNDEBUG -O2 -fno-strict-aliasing -pipe -march=pentium4 -D__wchar_t=wchar_t -DTHREAD_STACK_SIZE=0x20000 -O2 -fno-strict-aliasing -pipe -march=pentium4 -fPIC -I/usr/X11R6/include -I/usr/local/include/python2.4 -c ode_notrimesh.c -o build/temp.freebsd-6.1-RELEASE-p12-i386-2.4/ode_notrimesh.o ode_notrimesh.c: In function '__pyx_f_3ode_4Body_getMass': ode_notrimesh.c:3776: error: invalid lvalue in assignment ode_notrimesh.c:3784: error: invalid lvalue in assignment ode_notrimesh.c: In function '__pyx_f_3ode_9BallJoint___new__': ode_notrimesh.c:5973: error: invalid lvalue in assignment ode_notrimesh.c:5988: error: invalid lvalue in assignment ode_notrimesh.c: In function '__pyx_f_3ode_10HingeJoint___new__': ode_notrimesh.c:6272: error: invalid lvalue in assignment ode_notrimesh.c:6287: error: invalid lvalue in assignment ode_notrimesh.c: In function '__pyx_f_3ode_11SliderJoint___new__': ode_notrimesh.c:6747: error: invalid lvalue in assignment ode_notrimesh.c:6762: error: invalid lvalue in assignment ode_notrimesh.c: In function '__pyx_f_3ode_14UniversalJoint___new__': ode_notrimesh.c:7084: error: invalid lvalue in assignment ode_notrimesh.c:7099: error: invalid lvalue in assignment ode_notrimesh.c: In function '__pyx_f_3ode_11Hinge2Joint___new__': ode_notrimesh.c:7601: error: invalid lvalue in assignment ode_notrimesh.c:7616: error: invalid lvalue in assignment ode_notrimesh.c: In function '__pyx_f_3ode_10FixedJoint___new__': ode_notrimesh.c:8196: error: invalid lvalue in assignment ode_notrimesh.c:8211: error: invalid lvalue in assignment ode_notrimesh.c: In function '__pyx_f_3ode_12ContactJoint___new__': ode_notrimesh.c:8326: error: invalid lvalue in assignment ode_notrimesh.c:8342: error: invalid lvalue in assignment ode_notrimesh.c: In function '__pyx_f_3ode_6AMotor___new__': ode_notrimesh.c:8439: error: invalid lvalue in assignment ode_notrimesh.c:8454: error: invalid lvalue in assignment ode_notrimesh.c: In function '__pyx_f_3ode_11SimpleSpace___new__': ode_notrimesh.c:10682: error: invalid lvalue in assignment ode_notrimesh.c:10696: error: invalid lvalue in assignment ode_notrimesh.c: In function '__pyx_f_3ode_9HashSpace___new__': ode_notrimesh.c:10771: error: invalid lvalue in assignment ode_notrimesh.c:10785: error: invalid lvalue in assignment ode_notrimesh.c: In function '__pyx_f_3ode_13QuadTreeSpace___new__': ode_notrimesh.c:10969: error: invalid lvalue in assignment ode_notrimesh.c:10983: error: invalid lvalue in assignment ode_notrimesh.c: In function '__pyx_f_3ode_10GeomSphere___new__': ode_notrimesh.c:11195: error: invalid lvalue in assignment ode_notrimesh.c:11209: error: invalid lvalue in assignment ode_notrimesh.c: In function '__pyx_f_3ode_7GeomBox___new__': ode_notrimesh.c:11455: error: invalid lvalue in assignment ode_notrimesh.c:11469: error: invalid lvalue in assignment ode_notrimesh.c: In function '__pyx_f_3ode_9GeomPlane___new__': ode_notrimesh.c:11768: error: invalid lvalue in assignment ode_notrimesh.c:11782: error: invalid lvalue in assignment ode_notrimesh.c: In function '__pyx_f_3ode_13GeomCCylinder___new__': ode_notrimesh.c:12066: error: invalid lvalue in assignment ode_notrimesh.c:12080: error: invalid lvalue in assignment ode_notrimesh.c: In function '__pyx_f_3ode_7GeomRay___new__': ode_notrimesh.c:12346: error: invalid lvalue in assignment ode_notrimesh.c:12360: error: invalid lvalue in assignment ode_notrimesh.c: In function '__pyx_f_3ode_13GeomTransform___new__': ode_notrimesh.c:12650: error: invalid lvalue in assignment ode_notrimesh.c:12664: error: invalid lvalue in assignment ode_notrimesh.c: In function '__pyx_f_3ode_collide': ode_notrimesh.c:13091: error: invalid lvalue in assignment ode_notrimesh.c:13138: error: invalid lvalue in assignment error: command 'gcc41' failed with exit status 1 *** Error code 1 --- cut --- -- Best regards, Dmitry Marakasov mailto:am...@am... |
From: Diez B. R. <die...@ar...> - 2007-01-31 12:47:01
|
On Wednesday 31 January 2007 12:23, Dmitry Marakasov wrote: > Hi! > > I'm maintaining FreeBSD port of py-ode. There are no problems when > building it with gcc 3.4, but when I try to use gcc 4.1 (which will be > introduced in new FreeBSD versions) instead, I get the following errors: > > Any clues on how this can be fixed? Just a guess: You might be better off asking that on the pyrex mailing lists, as PyODE uses pyrex to generate the C-code. Diez |
From: Dmitry M. <am...@am...> - 2007-02-09 21:22:56
|
* Diez B. Roggisch (die...@ar...) wrote: > On Wednesday 31 January 2007 12:23, Dmitry Marakasov wrote: > > I'm maintaining FreeBSD port of py-ode. There are no problems when > > building it with gcc 3.4, but when I try to use gcc 4.1 (which will be > > introduced in new FreeBSD versions) instead, I get the following errors: > > > > Any clues on how this can be fixed? > > Just a guess: You might be better off asking that on the pyrex mailing lists, > as PyODE uses pyrex to generate the C-code. Thanks for the hint! I found out that pyrex 0.9.4.1 (as opposed to 0.9.3) does generate correct C code, so I suggest py-ode developers to regenerate *.c in the distribution with newer pyrex and release a new tarball. As a temporary fix, one can just delete *.c files after unpacking py-ode, so they'll be regenerated when running setup.py. Pyrex >= 0.9.4.1 needs to be installed for that, of course. Thanks again for help. -- Best regards, Dmitry Marakasov mailto:am...@am... |
From: Timothy S. <tim...@gm...> - 2007-02-11 08:53:07
|
On 2/9/07, Dmitry Marakasov <am...@am...> wrote: > I found out that pyrex 0.9.4.1 (as opposed to 0.9.3) does generate > correct C code, so I suggest py-ode developers to regenerate *.c > in the distribution with newer pyrex and release a new tarball. We released PyODE 1.2.0 a few days ago. It was built with Pyrex 0.9.5.1a so it should work with GCC 4.1. -- Timothy |