robotpkg/wip/talos-ros-controllers bulk build results

Log for talos-ros-controllers-0.2.11 on Debian-8.2-x86_64: bulk.log (Back)

=> Checking for clear installation ===> Installing bootstrap dependencies for talos-ros-controllers-0.2.11 => Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/Debian-8.2-x86_64/All/digest-20080510.tgz => Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/Debian-8.2-x86_64/All/tnftp-20130505~ssl.tgz ===> Checking bootstrap dependencies for talos-ros-controllers-0.2.11 => Required robotpkg package digest>=20080510: digest-20080510 found => Required robotpkg package tnftp>=20091122: tnftp-20130505~ssl found => Required system package gzip: gzip-1.6 found => Required system package pax and tar archivers: pax found => Required system package pkg_install>=20110805.7: pkg_install-20110805.7 found ===> Done bootstrap-depends for talos-ros-controllers-0.2.11 ===> Installing full dependencies for talos-ros-controllers-0.2.11 => Dependency digest-20080510 already installed => Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/Debian-8.2-x86_64/All/ros-actionlib-1.11.9.tgz To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh => Dependency ros-catkin-0.6.9r2 already installed => Dependency ros-comm-1.11.20 already installed => Dependency ros-common-msgs-1.11.4 already installed => Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/Debian-8.2-x86_64/All/ros-control-msgs-1.3.1.tgz To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh => Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/Debian-8.2-x86_64/All/ros-control-toolbox-1.13.2r1.tgz To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh => Dependency ros-genmsg-0.5.3 already installed => Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/Debian-8.2-x86_64/All/ros-geometry-1.11.3r1.tgz To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh => Dependency ros-message-generation-0.2.10 already installed => Dependency ros-message-runtime-0.4.12 already installed => Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/Debian-8.2-x86_64/All/ros-pluginlib-1.10.1.tgz To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh => Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/Debian-8.2-x86_64/All/ros-robot-model-1.11.5.tgz To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh => Dependency ros-ros-1.11.4 already installed => Dependency ros-std-msgs-0.5.9 already installed => Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/Debian-8.2-x86_64/All/ros-xacro-1.9.2.tgz To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh => Installing /opt/robotpkg/var/lib/robotpkg/wip/packages/bsd/Debian-8.2-x86_64/All/talos-pal-hardware-interfaces-0.0.3.tgz To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh => Dependency talos-ros-control-0.2.10 already installed => Dependency tnftp-20130505~ssl already installed ===> Checking build options for talos-ros-controllers-0.2.11 => Building with no option. ===> Checking alternatives for talos-ros-controllers-0.2.11 => Use the GNU C++ compiler: c++-compiler provided by g++>=3 => Use the GNU C compiler: c-compiler provided by gcc>=3 => Use python-2.7: python>=2.5<3.7 provided by python27>=2.7<2.8 => Use ros indigo: ros>=groovy ros>=hydro provided by ros-indigo ===> Checking dependencies for talos-ros-controllers-0.2.11 => Required system package boost-headers>=1.34.1: boost-headers-1.55 found => Required system package boostlib-filesystem>=1.34.1: boost-libs-1.55.0 found => Required system package boostlib-iostreams>=1.34.1: boost-libs-1.55.0 found => Required system package boostlib-math>=1.34.1: boost-libs-1.55.0 found => Required system package boostlib-thread>=1.34.1: boost-libs-1.55.0 found => Required system package cmake>=2.8.3: cmake-3.0.2 found => Required system package eigen3>=3.0.0: eigen3-3.2.2 found => Required system package g++>=3: g++-4.9.2 found => Required system package gcc>=3: gcc-4.9.2 found => Required system package googletest: googletest found => Required system package libstdc++: libstdc++ found => Required system package pkg-config>=0.22: pkg-config-0.28 found => Required system package py27-empy>=3: py27-empy-3.3.2 found => Required system package py27-nose>=0.10: py27-nose-1.3.4 found => Required system package python27>=2.7<2.8: python27-2.7.9 found => Required system package tinyxml>=2: tinyxml-2.6.2 found => Required robotpkg package ros-actionlib>=1.11<1.12: ros-actionlib-1.11.9 found => Required robotpkg package ros-catkin>=0.6<0.7: ros-catkin-0.6.9r2 found => Required robotpkg package ros-comm>=1.11<1.12: ros-comm-1.11.20 found => Required robotpkg package ros-common-msgs>=1.11<1.12: ros-common-msgs-1.11.4 found => Required robotpkg package ros-control-msgs>=1.3<1.4: ros-control-msgs-1.3.1 found => Required robotpkg package ros-control-toolbox>=1.13<1.15: ros-control-toolbox-1.13.2r1 found => Required robotpkg package ros-genmsg>=0.5<0.6: ros-genmsg-0.5.3 found => Required robotpkg package ros-geometry>=1.11<1.12: ros-geometry-1.11.3r1 found => Required robotpkg package ros-message-generation>=0.2<0.3: ros-message-generation-0.2.10 found => Required robotpkg package ros-message-runtime>=0.4<0.5: ros-message-runtime-0.4.12 found => Required robotpkg package ros-pluginlib>=1.10<1.11: ros-pluginlib-1.10.1 found => Required robotpkg package ros-robot-model>=1.11<1.12: ros-robot-model-1.11.5 found => Required robotpkg package ros-ros>=1.11<1.12: ros-ros-1.11.4 found => Required robotpkg package ros-std-msgs>=0.5: ros-std-msgs-0.5.9 found => Required robotpkg package ros-xacro>=1.9<1.10: ros-xacro-1.9.2 found => Required robotpkg package talos-pal-hardware-interfaces>=0.0.2: talos-pal-hardware-interfaces-0.0.3 found => Required robotpkg package talos-ros-control>=0.2: talos-ros-control-0.2.10 found ===> Done depends for talos-ros-controllers-0.2.11 ===> Extracting for talos-ros-controllers-0.2.11 => SHA1 checksums OK => RMD160 checksums OK ===> Configuring for talos-ros-controllers-0.2.11 CMake Warning at /opt/openrobots/share/genmsg/cmake/genmsg-extras.cmake:46 (message): Unknown message generator specified in ROS_LANG_DISABLE: geneus Call Stack (most recent call first): /opt/openrobots/share/genmsg/cmake/genmsgConfig.cmake:190 (include) /opt/openrobots/share/gencpp/cmake/gencppConfig.cmake:165 (find_package) /opt/openrobots/share/message_generation/cmake/message_generationConfig.cmake:165 (find_package) /opt/openrobots/share/catkin/cmake/catkinConfig.cmake:75 (find_package) talos_mode_state_controller/CMakeLists.txt:4 (find_package) CMake Warning at /opt/openrobots/share/genmsg/cmake/genmsg-extras.cmake:46 (message): Unknown message generator specified in ROS_LANG_DISABLE: gennodejs Call Stack (most recent call first): /opt/openrobots/share/genmsg/cmake/genmsgConfig.cmake:190 (include) /opt/openrobots/share/gencpp/cmake/gencppConfig.cmake:165 (find_package) /opt/openrobots/share/message_generation/cmake/message_generationConfig.cmake:165 (find_package) /opt/openrobots/share/catkin/cmake/catkinConfig.cmake:75 (find_package) talos_mode_state_controller/CMakeLists.txt:4 (find_package) CMake Warning at /opt/openrobots/share/genmsg/cmake/genmsg-extras.cmake:46 (message): Unknown message generator specified in ROS_LANG_DISABLE: geneus Call Stack (most recent call first): /opt/openrobots/share/genmsg/cmake/genmsgConfig.cmake:190 (include) /opt/openrobots/share/gencpp/cmake/gencppConfig.cmake:165 (find_package) /opt/openrobots/share/message_generation/cmake/message_generationConfig.cmake:165 (find_package) /opt/openrobots/share/catkin/cmake/catkinConfig.cmake:75 (find_package) talos_temperature_sensor_controller/CMakeLists.txt:4 (find_package) CMake Warning at /opt/openrobots/share/genmsg/cmake/genmsg-extras.cmake:46 (message): Unknown message generator specified in ROS_LANG_DISABLE: gennodejs Call Stack (most recent call first): /opt/openrobots/share/genmsg/cmake/genmsgConfig.cmake:190 (include) /opt/openrobots/share/gencpp/cmake/gencppConfig.cmake:165 (find_package) /opt/openrobots/share/message_generation/cmake/message_generationConfig.cmake:165 (find_package) /opt/openrobots/share/catkin/cmake/catkinConfig.cmake:75 (find_package) talos_temperature_sensor_controller/CMakeLists.txt:4 (find_package) CMake Warning at /opt/openrobots/share/genmsg/cmake/genmsg-extras.cmake:46 (message): Unknown message generator specified in ROS_LANG_DISABLE: geneus Call Stack (most recent call first): /opt/openrobots/share/genmsg/cmake/genmsgConfig.cmake:190 (include) /opt/openrobots/share/actionlib_msgs/cmake/actionlib_msgs-extras.cmake:2 (find_package) /opt/openrobots/share/actionlib_msgs/cmake/actionlib_msgsConfig.cmake:190 (include) /opt/openrobots/share/control_msgs/cmake/control_msgsConfig.cmake:165 (find_package) /opt/openrobots/share/catkin/cmake/catkinConfig.cmake:75 (find_package) talos_effort_controllers/CMakeLists.txt:19 (find_package) CMake Warning at /opt/openrobots/share/genmsg/cmake/genmsg-extras.cmake:46 (message): Unknown message generator specified in ROS_LANG_DISABLE: gennodejs Call Stack (most recent call first): /opt/openrobots/share/genmsg/cmake/genmsgConfig.cmake:190 (include) /opt/openrobots/share/actionlib_msgs/cmake/actionlib_msgs-extras.cmake:2 (find_package) /opt/openrobots/share/actionlib_msgs/cmake/actionlib_msgsConfig.cmake:190 (include) /opt/openrobots/share/control_msgs/cmake/control_msgsConfig.cmake:165 (find_package) /opt/openrobots/share/catkin/cmake/catkinConfig.cmake:75 (find_package) talos_effort_controllers/CMakeLists.txt:19 (find_package) CMake Warning at /opt/openrobots/share/genmsg/cmake/genmsg-extras.cmake:46 (message): Unknown message generator specified in ROS_LANG_DISABLE: geneus Call Stack (most recent call first): /opt/openrobots/share/genmsg/cmake/genmsgConfig.cmake:190 (include) /opt/openrobots/share/gencpp/cmake/gencppConfig.cmake:165 (find_package) /opt/openrobots/share/message_generation/cmake/message_generationConfig.cmake:165 (find_package) /opt/openrobots/share/catkin/cmake/catkinConfig.cmake:75 (find_package) talos_diff_drive_controllers/CMakeLists.txt:4 (find_package) CMake Warning at /opt/openrobots/share/genmsg/cmake/genmsg-extras.cmake:46 (message): Unknown message generator specified in ROS_LANG_DISABLE: gennodejs Call Stack (most recent call first): /opt/openrobots/share/genmsg/cmake/genmsgConfig.cmake:190 (include) /opt/openrobots/share/gencpp/cmake/gencppConfig.cmake:165 (find_package) /opt/openrobots/share/message_generation/cmake/message_generationConfig.cmake:165 (find_package) /opt/openrobots/share/catkin/cmake/catkinConfig.cmake:75 (find_package) talos_diff_drive_controllers/CMakeLists.txt:4 (find_package) CMake Warning at /opt/openrobots/share/genmsg/cmake/genmsg-extras.cmake:46 (message): Unknown message generator specified in ROS_LANG_DISABLE: geneus Call Stack (most recent call first): /opt/openrobots/share/genmsg/cmake/genmsgConfig.cmake:190 (include) /opt/openrobots/share/actionlib_msgs/cmake/actionlib_msgs-extras.cmake:2 (find_package) /opt/openrobots/share/actionlib_msgs/cmake/actionlib_msgsConfig.cmake:190 (include) /opt/openrobots/share/actionlib/cmake/actionlibConfig.cmake:165 (find_package) /opt/openrobots/share/catkin/cmake/catkinConfig.cmake:75 (find_package) talos_joint_trajectory_controller/CMakeLists.txt:51 (find_package) CMake Warning at /opt/openrobots/share/genmsg/cmake/genmsg-extras.cmake:46 (message): Unknown message generator specified in ROS_LANG_DISABLE: gennodejs Call Stack (most recent call first): /opt/openrobots/share/genmsg/cmake/genmsgConfig.cmake:190 (include) /opt/openrobots/share/actionlib_msgs/cmake/actionlib_msgs-extras.cmake:2 (find_package) /opt/openrobots/share/actionlib_msgs/cmake/actionlib_msgsConfig.cmake:190 (include) /opt/openrobots/share/actionlib/cmake/actionlibConfig.cmake:165 (find_package) /opt/openrobots/share/catkin/cmake/catkinConfig.cmake:75 (find_package) talos_joint_trajectory_controller/CMakeLists.txt:51 (find_package) CMake Error at /opt/openrobots/share/catkin/cmake/catkinConfig.cmake:75 (find_package): Could not find a package configuration file provided by "cmake_modules" with any of the following names: cmake_modulesConfig.cmake cmake_modules-config.cmake Add the installation prefix of "cmake_modules" to CMAKE_PREFIX_PATH or set "cmake_modules_DIR" to a directory containing one of the above files. If "cmake_modules" provides a separate development package or SDK, be sure it has been installed. Call Stack (most recent call first): talos_joint_trajectory_controller/CMakeLists.txt:51 (find_package) An unexpected error occured. The last 10 log lines are shown below. | "cmake_modules_DIR" to a directory containing one of the above files. If | "cmake_modules" provides a separate development package or SDK, be sure it | has been installed. | Call Stack (most recent call first): | talos_joint_trajectory_controller/CMakeLists.txt:51 (find_package) | | | -- Configuring incomplete, errors occurred! | See also "/local/robotpkg/var/tmp/robotpkg/wip/talos-ros-controllers/work/talos_ros_controllers-0.2.11/build/CMakeFiles/CMakeOutput.log". | See also "/local/robotpkg/var/tmp/robotpkg/wip/talos-ros-controllers/work/talos_ros_controllers-0.2.11/build/CMakeFiles/CMakeError.log". For details or bug reports, check the complete log file in: /local/robotpkg/var/tmp/robotpkg/wip/talos-ros-controllers/work/configure.log make[3]: *** [do-configure-cmake] Error 1 /local/robotpkg/var/lib/robotpkg/mk/configure/cmake-configure.mk:100: recipe for target 'do-configure-cmake' failed /local/robotpkg/var/lib/robotpkg/mk/pkg/package.mk:42: recipe for target 'pkg-check-installed' failed => Marking talos-ros-controllers-0.2.11 as broken make[2]: *** [pkg-check-installed] Error 2 ERROR: make: *** [package] Error 2 ===> Deinstalling for talos-ros-controllers Removed digest-20080510 Removing dependency ros-catkin-0.6.9r2 Removing dependency ros-comm-1.11.20 Removing dependency ros-common-msgs-1.11.4 Removing dependency ros-genmsg-0.5.3 Removing dependency ros-message-generation-0.2.10 Removing dependency ros-message-runtime-0.4.12 Removing dependency ros-std-msgs-0.5.9 Removing dependency Removing dependency ros-geometry2-0.5.15 Removing dependency ros-geometry-1.11.3r1 Removing dependency ros-robot-model-1.11.5 Removing dependency talos-ros-control-0.2.10 Removing dependency talos-pal-hardware-interfaces-0.0.3 Removed ros-actionlib-1.11.9 Removing dependency py27-catkin-pkg-0.2.4 Removing dependency Removing dependency ros-lint-0.9.2 Removing dependency ros-xacro-1.9.2 Removing dependency ros-roscpp-core-0.5.4r1 Removing dependency ros-genmsg-0.5.3 Removing dependency ros-genpy-0.5.3 Removing dependency ros-message-runtime-0.4.12 Removing dependency ros-genlisp-0.4.14 Removing dependency ros-gencpp-0.5.2 Removing dependency ros-message-generation-0.2.10 Removing dependency ros-std-msgs-0.5.9 Removing dependency ros-common-msgs-1.11.4 Removing dependency ros-control-msgs-1.3.1 Removed ros-catkin-0.6.9r2 Removed tnftp-20130505~ssl