The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
It is some kind of permission error, but it doesn't say what the object is or what permission is required.
From:
CMake Error at /opt/ros/indigo/share/catkin/cmake/safe_execute_process.cmake:11 (message): execute_process(/usr/bin/python "/home/ubuntu/catkin_ws/build/catkin_generated/generate_cached_setup.py")
I'd guess that either /usr/bin/python is no longer accessible to / executable by the user invoking catkin_make (doubtful), or that /home/ubuntu/catkin_ws/build/catkin_generated/generate_cached_setup.py now can't be read.
[..] I made some file permission changes [..]
Can you add the output of ls -al /home/ubuntu/catkin_ws/build/catkin_generated/generate_cached_setup.py and maybe also ls -al /home/ubuntu/catkin_ws/build to your question (use the edit button).
Make sure /home/ubuntu/catkin_ws and it's sub directories are (at least) readable by the ubuntu user. If in doubt (and you can afford the time), just remove the build and devel directories and rebuild everything (seeing as you are on arm that may take a while though / not be what you want).
| | 2 | No.2 Revision |
It is some kind of permission error, but it doesn't say what the object is or what permission is required.
From:
CMake Error at /opt/ros/indigo/share/catkin/cmake/safe_execute_process.cmake:11 (message): execute_process(/usr/bin/python "/home/ubuntu/catkin_ws/build/catkin_generated/generate_cached_setup.py")
I'd guess that either /usr/bin/python is no longer accessible to / executable by the user invoking catkin_make (doubtful), or that /home/ubuntu/catkin_ws/build/catkin_generated/generate_cached_setup.py now can't be read.
[..] I made some file permission changes [..]
Can you add the output of ls -al /home/ubuntu/catkin_ws/build/catkin_generated/generate_cached_setup.py and maybe also ls -al /home/ubuntu/catkin_ws/build to your question (use the edit button).
Make sure /home/ubuntu/catkin_ws and it's sub directories are (at least) readable by the ubuntu user. If in doubt (and you can afford the time), just remove the build and devel directories and rebuild everything (seeing as you are on arm that may take a while though / not be what you want).
Edit: devel/env.sh is indeed executable on my system. I don't know why it isn't on yours. It is being regenerated, and apparently its recreated without the executable bit set.
I ran the following 3 commands to try to sort things out, but it didn't help:
sudo find /usr/lib/python2.7 -exec chmod 777 {} \; sudo find /home/ubuntu -exec chmod go+rw {} \; sudo find /opt/ros/indigo/lib -exec chmod 777 {} \;
Even if they did, it would not really have been a solution. Changing permissions on system dirs (or any dirs really) like this is really (really) not recommended.
Looking at your build dir, it would seem you have relatively few pkgs in your catkin_ws. We can try and sort things out (the long way), or you could just rm -rf devel && rm -rf build and see whether running catkin_make now works (the quicker way).
No guarantees though, as your system seems to be in a rather strange state.
| | 3 | No.3 Revision |
It is some kind of permission error, but it doesn't say what the object is or what permission is required.
From:
CMake Error at /opt/ros/indigo/share/catkin/cmake/safe_execute_process.cmake:11 (message): execute_process(/usr/bin/python "/home/ubuntu/catkin_ws/build/catkin_generated/generate_cached_setup.py")
I'd guess that either /usr/bin/python is no longer accessible to / executable by the user invoking catkin_make (doubtful), or that /home/ubuntu/catkin_ws/build/catkin_generated/generate_cached_setup.py now can't be read.
[..] I made some file permission changes [..]
Can you add the output of ls -al /home/ubuntu/catkin_ws/build/catkin_generated/generate_cached_setup.py and maybe also ls -al /home/ubuntu/catkin_ws/build to your question (use the edit button).
Make sure /home/ubuntu/catkin_ws and it's sub directories are (at least) readable by the ubuntu user. If in doubt (and you can afford the time), just remove the build and devel directories and rebuild everything (seeing as you are on arm that may take a while though / not be what you want).
Edit: devel/env.sh is indeed executable on my system. I don't know why it isn't on yours. It is being regenerated, and apparently its recreated without the executable bit set.
I ran the following 3 commands to try to sort things out, but it didn't help:
sudo find /usr/lib/python2.7 -exec chmod 777 {} \; sudo find /home/ubuntu -exec chmod go+rw {} \; sudo find /opt/ros/indigo/lib -exec chmod 777 {} \;
Even if they did, it would not really have been a solution. Changing permissions on system dirs (or any dirs really) like this is really (really) not recommended.
Looking at your build dir, it would seem you have relatively few pkgs in your catkin_ws. We can try and sort things out (the long way), or you could just rm -rf devel && rm -rf build and see whether running catkin_make now works (the quicker way).
No guarantees though, as your system seems to be in a rather strange state.
Edit2:
Ok, I removed everything and reinitialized the catkin workspace, then ran catkin_make on the empty workspace. It still failed exactly as before. Any more ideas?
I can only assume that if you changed permissions on other parts of your system like you did with /usr/lib/python2.7 and /opt/ros/indigo/lib, that something is really borked.
Perhaps @Dirk Thomas can provide some help with the "env.sh does not receive executable permissions" issue.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
