On February 9, 2015 4:10:00 PM CST, David Boddie <[email protected]> wrote: >On Mon Feb 9 16:33:23 CET 2015, Cyd Haselton wrote: > >> >>> import time >> Traceback (most recent call last): >> File "<stdin>", line 1, in <module> >> ImportError: dlopen failed: library "/usr/python/lib/python3.4/lib- >dynload/time.cpython-34m.so" not found >> >> I've checked the referenced path and that file is there. Any ideas >why >> it...and every other module in the python3.4/lib-dynload >folder...fails to >> load? > >It sounds trivial, but are they actually built for the correct >architecture? > >On a desktop Linux system you could run "file" on the binary to get >some idea >of what the .so files are. I'm not sure what you can run in the >environment >you are using. >
They are. Here's the output for file /bld/python/Python-3.4.2 $ file /usr/python/lib/python3.4/lib-dynload/time.cpython-34m.so /usr/python/lib/python3.4/lib-dynload/time.cpython-34m.so: ELF 32-bit LSB shared object, ARM, version 1 (SYSV), dynamically linked, not stripped -- Sent from my Android device with K-9 Mail. Please excuse my brevity. _______________________________________________ Mobile-sig mailing list [email protected] https://mail.python.org/mailman/listinfo/mobile-sig
