Import error 1

>>> import ode
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: No module named ode

It means the ode module could not be found by the Python interpreter. If the module (file was built correctly it will be located in a directory named something like ~/ode-0.12/bindings/python/build/lib.linux-x86_64-2.7/. If that’s the case, you only forgot to execute:

~/ode-0.12/bindings/python$ sudo python install

which, among other things, copies build/lib.linux-x86_64-2.7/ to directory /usr/local/lib/python2.7/dist-packages.

Import error 2

It means the ode module could not be imported by the Python interpreter.

>>> import ode
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ImportError: cannot open shared object file: No such file or directory

This error is saying that ODE needs access access to the compiled library (as a shared object, e.g. but can’t find it. It is not about whether sys.path contains or not the location of the library.

Dynamically linked libraries are looked up in the system library path, i.e. the directories included in the LD_LIBRARY_PATH environment variable. However, instead of manually fixing this value, try running ldconfig –its job is to “configure dynamic linker run-time bindings” (man page)– and import ode again. Hopefully you’ll get no output, which means it was imported correctly.



If VTK looks to be installed correctly (e.g. it can be imported with no errors) but while running a program using VTK you get an error mentioning vtkXOpenGLRenderWindow, then probably you have an error related to your video card, its drivers and OpenGL. You can test the latter works fine by running the programs glxgears or glxinfo at the command line (if they are not found you can install them with sudo apt-get install mesa-utils).


If you can’t get OpenGL to work, then there is no way VTK will work in your system, and probably most visualization software won’t too.