ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

erniejunior's profile - activity

2015-03-21 10:07:01 -0500 received badge  Nice Question (source)
2013-05-28 22:04:21 -0500 received badge  Famous Question (source)
2012-11-28 10:14:00 -0500 received badge  Notable Question (source)
2012-11-03 02:22:01 -0500 received badge  Student (source)
2012-11-03 02:19:48 -0500 received badge  Popular Question (source)
2012-10-21 00:14:10 -0500 received badge  Editor (source)
2012-10-21 00:04:47 -0500 received badge  Organizer (source)
2012-10-20 03:35:25 -0500 asked a question compiling ROS on Debian

Hello,

I am trying to get started with ROS under debian. I followed the install instructions for debian until the point where it is compiled using make. There I run into trouble building the rxtools with the following error:

make[2]: * No rule to make target '/usr/lib/python3.2/config/libpython3.2.so', needed by `lib/_rxtoolscpp.so'. Stop.

make[1]: * [rx/rxtools/CMakeFiles/python_rxtools.dir/all] Error 2

make: * [all] Error 2

The folder 'rx/rxtools/CMakeFiles' does not exist in my ros-underlay folder! I also think it is strange, that libpython is built by ROS. I ran into some small, solvable problems during the installation process before, but I could not find anything about this error in the net and am kind of lost here.

Thank you in advance,

Maximilian

[Edit:] I did my research and found out that for some reason make wants to build libpython3.2.so which is already installed on my system.

A workaround for me was to remove the line "lib/_rxtoolscpp.so: /usr/lib/python3.2/config/libpython3.2.so" from the file build/rxtools/CMakeFiles/python_rxtools.dir/build.make and change "-lpython3.2" in build/rxtools/CMakeFiles/python_rxtools.dir/link.txt to "-L/usr/lib/python3.2/config/libpython3.2.so".

make and make install now runs without any errors but I do not think that this ugly fix is the right way to compile ROS. Maybe there is a problem with the CMake files somewhere and this could be a bug.