ros-naoqi / naoqi_dcm_driver

Hardware interface allowing control Nao, Romeo, and Pepper robots via ROS
4 stars 13 forks source link

naoqi_dcm_drivers does not compile on armhf #2

Open tfoote opened 7 years ago

tfoote commented 7 years ago

http://build.ros.org/view/Ibin_arm_uThf/job/Ibin_arm_uThf__naoqi_dcm_driver__ubuntu_trusty_armhf__binary/67/console

04:09:24 [100%] Building CXX object CMakeFiles/naoqi_dcm_driver.dir/src/motion.cpp.o
04:09:24 /usr/bin/arm-linux-gnueabihf-g++   -DLIBQI_VERSION=23 -DROSCONSOLE_BACKEND_LOG4CXX -DROS_PACKAGE_NAME=\"naoqi_dcm_driver\" -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -DNDEBUG -D_FORTIFY_SOURCE=2  -I/tmp/binarydeb/ros-indigo-naoqi-dcm-driver-0.0.2/include -I/opt/ros/indigo/include    -o CMakeFiles/naoqi_dcm_driver.dir/src/motion.cpp.o -c /tmp/binarydeb/ros-indigo-naoqi-dcm-driver-0.0.2/src/motion.cpp
04:11:02 Linking CXX executable devel/lib/naoqi_dcm_driver/naoqi_dcm_driver
04:11:02 /usr/bin/cmake -E cmake_link_script CMakeFiles/naoqi_dcm_driver.dir/link.txt --verbose=1
04:11:02 /usr/bin/arm-linux-gnueabihf-g++   -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -DNDEBUG -D_FORTIFY_SOURCE=2     CMakeFiles/naoqi_dcm_driver.dir/src/robot_driver.cpp.o CMakeFiles/naoqi_dcm_driver.dir/src/robot.cpp.o CMakeFiles/naoqi_dcm_driver.dir/src/tools.cpp.o CMakeFiles/naoqi_dcm_driver.dir/src/diagnostics.cpp.o CMakeFiles/naoqi_dcm_driver.dir/src/memory.cpp.o CMakeFiles/naoqi_dcm_driver.dir/src/dcm.cpp.o CMakeFiles/naoqi_dcm_driver.dir/src/motion.cpp.o  -o devel/lib/naoqi_dcm_driver/naoqi_dcm_driver -rdynamic /opt/ros/indigo/lib/libtf.so /opt/ros/indigo/lib/libtf2_ros.so /opt/ros/indigo/lib/libactionlib.so /opt/ros/indigo/lib/libmessage_filters.so /opt/ros/indigo/lib/libtf2.so /opt/ros/indigo/lib/libcontroller_manager.so /opt/ros/indigo/lib/librealtime_tools.so -ltinyxml /opt/ros/indigo/lib/libclass_loader.so -lPocoFoundation -ldl /opt/ros/indigo/lib/libroslib.so /opt/ros/indigo/lib/libqi.so /opt/ros/indigo/lib/libqicore.so /opt/ros/indigo/lib/libroscpp.so -lboost_signals -lboost_filesystem /opt/ros/indigo/lib/librosconsole.so /opt/ros/indigo/lib/librosconsole_log4cxx.so /opt/ros/indigo/lib/librosconsole_backend_interface.so -llog4cxx -lboost_regex /opt/ros/indigo/lib/libxmlrpcpp.so /opt/ros/indigo/lib/libroscpp_serialization.so /opt/ros/indigo/lib/librostime.so -lboost_date_time /opt/ros/indigo/lib/libcpp_common.so -lboost_system -lboost_thread -lpthread -lconsole_bridge /opt/ros/indigo/lib/libqi.so /opt/ros/indigo/lib/libqicore.so /opt/ros/indigo/lib/libroscpp.so -lboost_signals -lboost_filesystem /opt/ros/indigo/lib/librosconsole.so /opt/ros/indigo/lib/librosconsole_log4cxx.so /opt/ros/indigo/lib/librosconsole_backend_interface.so -llog4cxx -lboost_regex /opt/ros/indigo/lib/libxmlrpcpp.so /opt/ros/indigo/lib/libroscpp_serialization.so /opt/ros/indigo/lib/librostime.so -lboost_date_time /opt/ros/indigo/lib/libcpp_common.so -lboost_system -lboost_thread -lpthread -lconsole_bridge -Wl,-rpath,/opt/ros/indigo/lib: 
04:11:05 /opt/ros/indigo/lib/libqi.so: undefined reference to `boost::atomics::detail::lockpool::get_lock_for(void const volatile*)'
04:11:05 collect2: error: ld returned 1 exit status
04:11:05 make[4]: *** [devel/lib/naoqi_dcm_driver/naoqi_dcm_driver] Error 1
04:11:05 make[4]: Leaving directory `/tmp/binarydeb/ros-indigo-naoqi-dcm-driver-0.0.2/obj-arm-linux-gnueabihf'
04:11:05 make[3]: *** [CMakeFiles/naoqi_dcm_driver.dir/all] Error 2
04:11:05 make[3]: Leaving directory `/tmp/binarydeb/ros-indigo-naoqi-dcm-driver-0.0.2/obj-arm-linux-gnueabihf'
04:11:05 make[2]: *** [all] Error 2
04:11:05 make[2]: Leaving directory `/tmp/binarydeb/ros-indigo-naoqi-dcm-driver-0.0.2/obj-arm-linux-gnueabihf'
04:11:05 dh_auto_build: make -j1 returned exit code 2
04:11:05 make[1]: *** [override_dh_auto_build] Error 2
04:11:05 make[1]: Leaving directory `/tmp/binarydeb/ros-indigo-naoqi-dcm-driver-0.0.2'
04:11:05 make: *** [build] Error 2
04:11:05 dpkg-buildpackage: error: debian/rules build gave error exit status 2
04:11:05 E: Building failed
04:11:05 Traceback (most recent call last):
04:11:05   File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 133, in build_binarydeb
04:11:05     subprocess.check_call(cmd, cwd=source_dir)
04:11:05   File "/usr/lib/python3.4/subprocess.py", line 561, in check_call
04:11:05     raise CalledProcessError(retcode, cmd)
04:11:05 subprocess.CalledProcessError: Command '['apt-src', 'build', 'ros-indigo-naoqi-dcm-driver']' returned non-zero exit status 1
04:11:05 # END SUBSECTION
04:11:05 
04:11:05 --------------------------------------------------------------------------------------------------
04:11:05 `apt-src build ros-indigo-naoqi-dcm-driver` failed.
04:11:05 This is usually because of an error building the package.
04:11:05 The traceback from this failure (just above) is printed for completeness, but you can ignore it.
04:11:05 You should look above `E: Building failed` in the build log for the actual cause of the failure.
04:11:05 --------------------------------------------------------------------------------------------------
04:11:05