Le 22/04/2013 22:25, jholg@gmx.de a écrit :
Hi,
On Monday, April 22, 2013 19:09:00 Stefan Behnel wrote:
Holger Joukl, 22.04.2013 12:49:
"etree.cpython-32mu.so" So maybe you're building a 32bit target and try to use it on (non 32bit-enabled) 64bit system?
The "32" in "etree.cpython-32mu.so" just refers to the CPython version. Recent Py3 versions make it easier to install shared libraries in system specific versions by encoding version information in the file name. Oh, I see, thanks for clarification. Working with too freakin' old Python versions, I am still
But the ldd failing to interpret the file error sounds just like s.th. I encountered lately, which indeed stemmed from a 32 vs 64bit situation in my case.
The 'file' tool should be able to identify the architecture of a .so file, independently of the architecture running the tool. -- Simon Sapin