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 |
That's quite a noisy output!
The words not found appear 120 times in that blurb. It looks like it's related specifically to /bin/sh which is just the basic Linux shell. The shell isn't finding most of that stuff which means this is probably related to a Linux PATH environment variable.
Did you source the ROS2 setup file beforehand? For Dashing I would expect it to be located somewhere like /opt/ros/dashing/setup.sh
I see a lot of references to your home directory. How have you installed ROS2? Do you have the /opt/ros2 directory? There is a separate archive of packages that the ROS2 "getting started" instructions tell everyone to install, but the intention for those, I think, is for you to install everything from that archive to /opt/ros2 using a few ROS2 and rosdep commands.
The main component which failed here, rosidl_generator_cpp, is for creating custom messages. By default you have access to things like std_msgs (these), but if you wish to create your own you need to work with rosidl. You can find more information on the ROS2 Dashing docs website, "Expanding on ROS 2 interfaces"
Another question: Is there a specific reason you're using Dashing rather than Foxy?
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.
