robotpkg/wip/sot-romeo-v3 bulk build results

=> Checking for clear installation ===> Installing bootstrap dependencies for sot-romeo-v3-2.0.1 => 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 sot-romeo-v3-2.0.1 => 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.9: pkg_install-20110805.9 found ===> Done bootstrap-depends for sot-romeo-v3-2.0.1 ===> Installing full dependencies for sot-romeo-v3-2.0.1 => Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/CentOS-7-x86_64/All/console-bridge-0.2.7.tgz => Dependency digest-20080510 already installed => Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/CentOS-7-x86_64/All/dynamic-graph-bridge-msgs-0.2.0.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 => Installing /opt/robotpkg/var/lib/robotpkg/wip/packages/bsd/CentOS-7-x86_64/All/dynamic-graph-bridge-v3-3.0.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 => Dependency dynamic-graph-v3-3.0.1 already installed => Dependency py27-dynamic-graph-v3-3.0.2 already installed => Dependency py27-sot-tools-v3-2.0.3 already installed => Dependency ros-comm-1.11.20 already installed => Dependency ros-message-runtime-0.4.12 already installed => Dependency ros-rospack-2.2.4 already installed => Dependency ros-std-msgs-0.5.9 already installed => Dependency sot-core-v3-3.1.9r1 already installed => Dependency sot-dynamic-pinocchio-v3-3.1.8 already installed => Dependency tnftp-20130505~ssl already installed ===> Checking build options for sot-romeo-v3-2.0.1 => Building with no option. ===> Checking alternatives for sot-romeo-v3-2.0.1 => 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 sot-romeo-v3-2.0.1 => Required system package boost-headers>=1.34.1: boost-headers-1.53 found => Required system package boostlib-filesystem>=1.34.1: boost-libs-1.53.0 found => Required system package boostlib-iostreams>=1.34.1: boost-libs-1.53.0 found => Required system package boostlib-math>=1.34.1: boost-libs-1.53.0 found => Required system package boostlib-thread>=1.34.1: boost-libs-1.53.0 found => Required system package cmake>=2.6: cmake-2.8.12.2 found => Required system package doxygen>=1.5: doxygen-1.8.5 found => Required system package g++>=3: g++-4.8.5 found => Required system package gcc>=3: gcc-4.8.5 found => Required system package graphviz>=2: graphviz-2.30.1 found => Required system package libstdc++: libstdc++ found => Required system package pdflatex: pdflatex found => Required system package pkg-config>=0.22: pkg-config-0.27.1 found => Required system package python27>=2.7<2.8: python27-2.7.5 found => Required robotpkg package console-bridge>=0.1: console-bridge-0.2.7 found => Required robotpkg package dynamic-graph-bridge-msgs>=0.2.0: dynamic-graph-bridge-msgs-0.2.0 found => Required robotpkg package dynamic-graph-bridge-v3>=3.0.0: dynamic-graph-bridge-v3-3.0.9 found => Required robotpkg package dynamic-graph-v3>=3.0.0: dynamic-graph-v3-3.0.1 found => Required robotpkg package py27-dynamic-graph-v3>=3.0: py27-dynamic-graph-v3-3.0.2 found => Required robotpkg package py27-sot-tools-v3>=2.0: py27-sot-tools-v3-2.0.3 found => Required robotpkg package ros-comm>=1.11<1.12: ros-comm-1.11.20 found => Required robotpkg package ros-message-runtime>=0.4<0.5: ros-message-runtime-0.4.12 found => Required robotpkg package ros-rospack>=2.2<2.3: ros-rospack-2.2.4 found => Required robotpkg package ros-std-msgs>=0.5: ros-std-msgs-0.5.9 found => Required robotpkg package sot-core-v3>=3.0.0: sot-core-v3-3.1.9r1 found => Required robotpkg package sot-dynamic-pinocchio-v3>=3.1.1: sot-dynamic-pinocchio-v3-3.1.8 found WARNING: Using console-bridge in /opt/openrobots WARNING: The following packages may interfere with the build because they WARNING: are located in paths used by other dependencies: WARNING: console-bridge in /usr ===> Done depends for sot-romeo-v3-2.0.1 ===> Extracting for sot-romeo-v3-2.0.1 => SHA1 checksums OK => RMD160 checksums OK ===> Configuring for sot-romeo-v3-2.0.1 CMake Warning at cmake/python.cmake:36 (MESSAGE): CMake versions older than 3.2 do not properly find Python. Custom macros are used to find it. Call Stack (most recent call first): src/CMakeLists.txt:16 (INCLUDE) -- Doxygen rendering: using LaTeX backend ===> Building for sot-romeo-v3-2.0.1 /local/robotpkg/var/tmp/robotpkg/wip/sot-romeo-v3/work/sot-romeo-v3-2.0.1/src/sot-romeo-device.cpp: In member function 'void SoTRomeoDevice::setSensors(std::map, dynamicgraph::sot::NamedVector>&)': /local/robotpkg/var/tmp/robotpkg/wip/sot-romeo-v3/work/sot-romeo-v3-2.0.1/src/sot-romeo-device.cpp:62:7: warning: unused variable 't' [-Wunused-variable] int t = stateSOUT.getTime () + 1; ^ /local/robotpkg/var/tmp/robotpkg/wip/sot-romeo-v3/work/sot-romeo-v3-2.0.1/src/sot-romeo-device.cpp: In member function 'void SoTRomeoDevice::getControl(std::map, dynamicgraph::sot::NamedVector>&)': /local/robotpkg/var/tmp/robotpkg/wip/sot-romeo-v3/work/sot-romeo-v3-2.0.1/src/sot-romeo-device.cpp:152:39: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] if (anglesOut.size()!=state_.size()-6) ^ /local/robotpkg/var/tmp/robotpkg/wip/sot-romeo-v3/work/sot-romeo-v3-2.0.1/src/sot-romeo-controller.cpp: In function 'dynamicgraph::sot::AbstractSotExternalInterface* createSotExternalInterface()': /local/robotpkg/var/tmp/robotpkg/wip/sot-romeo-v3/work/sot-romeo-v3-2.0.1/src/sot-romeo-controller.cpp:161:16: error: cannot allocate an object of abstract type 'SoTRomeoController' return new SoTRomeoController; ^ In file included from /local/robotpkg/var/tmp/robotpkg/wip/sot-romeo-v3/work/sot-romeo-v3-2.0.1/src/sot-romeo-controller.cpp:16:0: /local/robotpkg/var/tmp/robotpkg/wip/sot-romeo-v3/work/sot-romeo-v3-2.0.1/src/sot-romeo-controller.hh:25:7: note: because the following virtual functions are pure within 'SoTRomeoController': class SoTRomeoController: public ^ In file included from /local/robotpkg/var/tmp/robotpkg/wip/sot-romeo-v3/work/sot-romeo-v3-2.0.1/src/sot-romeo-controller.hh:19:0, from /local/robotpkg/var/tmp/robotpkg/wip/sot-romeo-v3/work/sot-romeo-v3-2.0.1/src/sot-romeo-controller.cpp:16: /opt/openrobots/include/sot/core/abstract-sot-external-interface.hh:73:20: note: virtual void dynamicgraph::sot::AbstractSotExternalInterface::setSecondOrderIntegration() virtual void setSecondOrderIntegration(void)=0; ^ /opt/openrobots/include/sot/core/abstract-sot-external-interface.hh:74:20: note: virtual void dynamicgraph::sot::AbstractSotExternalInterface::setNoIntegration() virtual void setNoIntegration(void)=0; ^ /local/robotpkg/var/tmp/robotpkg/wip/sot-romeo-v3/work/sot-romeo-v3-2.0.1/src/sot-romeo-controller.cpp:162:3: warning: control reaches end of non-void function [-Wreturn-type] } ^ make[2]: *** [src/CMakeFiles/sot-romeo-controller.dir/sot-romeo-controller.cpp.o] Error 1 make[2]: *** Waiting for unfinished jobs.... make[1]: *** [src/CMakeFiles/sot-romeo-controller.dir/all] Error 2 make: *** [all] Error 2 An unexpected error occured. The last 10 log lines are shown below. | ^ | /local/robotpkg/var/tmp/robotpkg/wip/sot-romeo-v3/work/sot-romeo-v3-2.0.1/src/sot-romeo-controller.cpp:162:3: warning: control reaches end of non-void function [-Wreturn-type] | } | ^ | make[2]: *** [src/CMakeFiles/sot-romeo-controller.dir/sot-romeo-controller.cpp.o] Error 1 | make[2]: *** Waiting for unfinished jobs.... | make[2]: Leaving directory `/local/robotpkg/var/tmp/robotpkg/wip/sot-romeo-v3/work/sot-romeo-v3-2.0.1' | make[1]: Leaving directory `/local/robotpkg/var/tmp/robotpkg/wip/sot-romeo-v3/work/sot-romeo-v3-2.0.1' | make[1]: *** [src/CMakeFiles/sot-romeo-controller.dir/all] Error 2 | make: *** [all] Error 2 For details or bug reports, check the complete log file in: /local/robotpkg/var/tmp/robotpkg/wip/sot-romeo-v3/work/build.log make[3]: *** [do-build] Error 1 make[2]: *** [pkg-check-installed] Error 2 => Marking sot-romeo-v3-2.0.1 as broken ERROR: make: *** [package] Error 2 ===> Deinstalling for sot-romeo-v3 Removing dependency urdfdom-0.3.0r2 Removing dependency pinocchio-1.2.9r1 Removing dependency py27-pinocchio-1.2.9 Removing dependency sot-dynamic-pinocchio-v3-3.1.8 Removing dependency ros-roscpp-core-0.5.4r1 Removing dependency ros-message-runtime-0.4.12 Removing dependency ros-std-msgs-0.5.9 Removing dependency ros-common-msgs-1.11.4 Removing dependency ros-comm-msgs-1.11.2r1 Removing dependency ros-comm-1.11.20 Removing dependency ros-realtime-tools-1.9.2 Removing dependency ros-actionlib-1.11.9 Removing dependency ros-geometry2-0.5.15 Removing dependency ros-geometry-1.11.3r1 Removing dependency dynamic-graph-bridge-msgs-0.2.0 Removing dependency dynamic-graph-bridge-v3-3.0.9 Removed console-bridge-0.2.7 Removed digest-20080510 Removed tnftp-20130505~ssl