Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

It looks like you have the geometry stack checked out into you local workspace, and you have your local workspace set up as an overlay on the system install, which is why it's preferring your local copy over the system install of tf.

The tf python module is implemented in C++, which is why you can get dynamic linker errors when trying to load it.

There are two things that could be causing this linking error, both related to ABI problems:

  • You've upgraded some of your ROS packages, but not all of them, and somewhere along the way an ABI problem crept in. This should go away if you do an apt-get update and apt-get dist-upgrade to install the latest versions of everything.
  • You've upgraded your ROS packages since building tf, and the ABI of one of the packages it depends on has changed. You can try removing the build and devel folders in your workspace and rebuilding everything.

It looks like you have the geometry stack (which contains tf) checked out into you local workspace, and you have your local workspace set up as an overlay on the system install, which is why it's preferring your local copy over the system install of tf.

The tf python module is implemented in C++, which is why you can get dynamic linker errors when trying to load it.

There are two things that could be causing this linking error, both related to ABI problems:

  • You've upgraded some of your ROS packages, but not all of them, and somewhere along the way an ABI problem crept in. This should go away if you do an apt-get update and apt-get dist-upgrade to install the latest versions of everything.
  • You've upgraded your ROS packages since building tf, and the ABI of one of the packages it depends on has changed. You can try removing the build and devel folders in your workspace and rebuilding everything.