Bug#383868: libode0c2: python-soya reports undefined symbol in ode when trying to load ode module
Coin, Sorry for being late, i'm way too busy these days... Guus Sliepen [EMAIL PROTECTED] writes: 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. We should really have upstream do some more efforts to handle the soname bump correctly. Can't you bump it yourself and ask him to patch 0.6, which is to be considered buggy ? 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? No, upstream people are unaware of it. Soya was recently fixed by a bugreporter, so some bugs may still remain. Upstream authors are quite willing to accept patches, and the latest is already included, but there is absolutly no work done on 64bits architectures, as noone has such a machine to test it. I'm asking them for the 0.6 move, but the ODE-master of Soya seems to be away on holidays, so we'll have to be patient. In the past, linking both with static and dynamic librarie to create a new library led to horrible results, so i'd like to avoid this situation. Remember i was the one who strongly asked for a dynamic libode in the past. Stay tuned... -- Marc Dequènes (Duck) pgpbhsjRBCVEQ.pgp Description: PGP signature
Bug#383868: libode0c2: python-soya reports undefined symbol in ode when trying to load ode module
Package: libode0c2 Version: 1:0.5-5 Severity: normal 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. Thank you in advance -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Versions of packages libode0c2 depends on: ii libc62.3.6.ds1-2 GNU C Library: Shared libraries ii libgcc1 1:4.1.1-11 GCC support library ii libstdc++6 4.1.1-11The GNU Standard C++ Library v3 libode0c2 recommends no packages. -- no debconf information
Bug#383868: libode0c2: python-soya reports undefined symbol in ode when trying to load ode module
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
