robotpkg/wip/talos-pal-transmissions bulk build results
Log for talos-pal-transmissions-0.2.3 on CentOS-7-x86_64: bulk.log (Back)
=> Checking for clear installation
===> Installing bootstrap dependencies for talos-pal-transmissions-0.2.3
=> Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/CentOS-7-x86_64/All/digest-20080510.tgz
=> Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/CentOS-7-x86_64/All/tnftp-20130505~ssl.tgz
===> Checking bootstrap dependencies for talos-pal-transmissions-0.2.3
=> Required robotpkg package digest>=20080510: digest-20080510 found
=> Required robotpkg package tnftp>=20091122: tnftp-20130505~ssl found
=> Required system package gzip: gzip-1.5 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-pal-transmissions-0.2.3
===> Installing full dependencies for talos-pal-transmissions-0.2.3
=> Dependency digest-20080510 already installed
=> Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/CentOS-7-x86_64/All/ros-catkin-0.6.9r2.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/CentOS-7-x86_64/All/ros-comm-1.11.20.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
=> Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/CentOS-7-x86_64/All/ros-common-msgs-1.11.4.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
=> Dependency ros-genmsg-0.5.3 already installed
=> Dependency ros-message-generation-0.2.10 already installed
=> Dependency ros-message-runtime-0.4.12 already installed
=> Dependency ros-std-msgs-0.5.9 already installed
=> Installing /opt/robotpkg/var/lib/robotpkg/wip/packages/bsd/CentOS-7-x86_64/All/talos-ros-control-0.2.10.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
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 tnftp-20130505~ssl already installed
===> Checking build options for talos-pal-transmissions-0.2.3
=> Building with no option.
===> Checking alternatives for talos-pal-transmissions-0.2.3
=> 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 provided by ros-indigo
===> Checking dependencies for talos-pal-transmissions-0.2.3
=> Required system package boost-headers>=1.34.1: boost-headers-1.53 found
=> Required system package boostlib-thread>=1.34.1: boost-libs-1.53.0 found
=> Required system package cmake>=2.8.3: cmake-2.8.12.2 found
=> Required system package g++>=3: g++-4.8.5 found
=> Required system package gcc>=3: gcc-4.8.5 found
=> Required system package googletest: googletest found
=> Required system package libstdc++: libstdc++ found
=> Required system package pkg-config>=0.22: pkg-config-0.27.1 found
=> Required system package py27-empy>=3: py27-empy-3.3.2 found
=> Required system package py27-nose>=0.10: py27-nose-1.3.7 found
=> Required system package python27>=2.7<2.8: python27-2.7.5 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-genmsg>=0.5<0.6: ros-genmsg-0.5.3 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-std-msgs>=0.5: ros-std-msgs-0.5.9 found
=> Required robotpkg package talos-ros-control>=0.2: talos-ros-control-0.2.10 found
===> Done depends for talos-pal-transmissions-0.2.3
===> Extracting for talos-pal-transmissions-0.2.3
=> SHA1 checksums OK
=> RMD160 checksums OK
===> Configuring for talos-pal-transmissions-0.2.3
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):
CMakeLists.txt:5 (find_package)
An unexpected error occured. The last 10 log lines are shown below.
| 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):
| CMakeLists.txt:5 (find_package)
|
|
For details or bug reports, check the complete log file in:
/local/robotpkg/var/tmp/robotpkg/wip/talos-pal-transmissions/work/configure.log
make[3]: *** [do-configure-cmake] Error 1
make[2]: *** [pkg-check-installed] Error 2
=> Marking talos-pal-transmissions-0.2.3 as broken
ERROR: make: *** [package] Error 2
===> Deinstalling for talos-pal-transmissions
Removed digest-20080510
Removing dependency py27-catkin-pkg-0.2.4
Removing dependency
Removing dependency ros-srdfdom-0.2.7
Removing dependency ros-random-numbers-0.2.0
Removing dependency ros-eigen-stl-containers-0.1.4
Removing dependency ros-class-loader-0.3.0
Removing dependency ros-orocos-kdl-1.3.0
Removing dependency ros-angles-1.9.9
Removing dependency ros-rospack-2.2.4
Removing dependency ros-roscpp-core-0.5.4r1
Removing dependency ros-genmsg-0.5.3
Removing dependency ros-ros-1.11.4
Removing dependency ros-python-qt-binding-0.2.14
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-shape-tools-0.2.1
Removing dependency ros-comm-msgs-1.11.2r1
Removing dependency ros-comm-1.11.20
Removing dependency ros-bond-core-1.7.14
Removing dependency ros-resource-retriever-1.11.5
Removing dependency ros-geometric-shapes-0.4.1
Removing dependency ros-console-bridge-0.4.2
Removing dependency ros-pluginlib-1.10.1
Removing dependency ros-realtime-tools-1.9.2
Removing dependency ros-dynamic-reconfigure-1.5.37
Removing dependency ros-nodelet-core-1.9.0
Removing dependency ros-qt-gui-core-0.2.25
Removing dependency ros-rqt-0.2.14
Removing dependency ros-control-toolbox-1.13.2r1
Removing dependency ros-actionlib-1.11.9
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
Removed ros-catkin-0.6.9r2
Removed tnftp-20130505~ssl