On Sun, Aug 20, 2006 at 11:24:07AM +0200, Isaac Clerencia wrote: > I'm trying to use ode from python-soya and I'm getting the following: > % cat ode.py > from soya import ode > ٢ [EMAIL PROTECTED]:/tmp/tutorial > % python ode.py > Traceback (most recent call last): > File "ode.py", line 1, in ? > from soya import ode > File "/var/lib/python-support/python2.4/soya/ode.py", line 4, in ? > from soya._ode import * > ImportError: /var/lib/python-support/python2.4/soya/_ode.so: > undefined symbol: dGeomTriMeshDataCreate > > I'm not sure if the bug is within libode or soya, but I would say ode, > otherwise reassign.
I disabled OPCODE support in the ode 0.5 package, because the code is
broken on 64 bit architectures. Ode 0.6 is out already, and it has a
working OPCODE for 64 bit architectures, however it is not compatible
with 0.5, and upstream did not bump the soname. My idea is to build a
static library of 0.6 only. However, currently all packages in Debian
depending on ODE seem to use 0.5, and they will become unbuildable if I
upload 0.6.
Marc, I Cc'ed this to you, I'd like your comments. Is python-soya's
upstream aware of the issues with OPCODE in 0.5, and/or are they
planning to move to 0.6? Is it possible for python-soya to link with a
static library?
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
