EvARobot: Huge error output while catkin_make

kinetic

asked 2019-01-23 06:36:36 -0500

metobom
27 ●8 ●11 ●13

 Hello I am trying to Install EvARobot to my Ubuntu 16.04. When I compile I get this huge output. Any ideas?

metobom@m3tobom:~$ cd ~/m3_ws
metobom@m3tobom:~/m3_ws$ catkin_make
Base path: /home/metobom/m3_ws
Source space: /home/metobom/m3_ws/src
Build space: /home/metobom/m3_ws/build
Devel space: /home/metobom/m3_ws/devel
Install space: /home/metobom/m3_ws/install
####
#### Running command: "make cmake_check_build_system" in "/home/metobom/m3_ws/build"
####
####
#### Running command: "make -j6 -l6" in "/home/metobom/m3_ws/build"
####
[  0%] Built target std_msgs_generate_messages_lisp
[  0%] Built target _controller_manager_msgs_generate_messages_check_deps_ListControllerTypes
[  0%] Built target _controller_manager_msgs_generate_messages_check_deps_SwitchController
[  0%] Built target _controller_manager_msgs_generate_messages_check_deps_ControllersStatistics
[  0%] Built target _controller_manager_msgs_generate_messages_check_deps_ControllerState
[  0%] Built target _controller_manager_msgs_generate_messages_check_deps_UnloadController
[  0%] Built target _controller_manager_msgs_generate_messages_check_deps_LoadController
[  0%] Built target std_msgs_generate_messages_nodejs
[  0%] Built target std_msgs_generate_messages_cpp
[  0%] Built target _controller_manager_msgs_generate_messages_check_deps_ListControllers
[  0%] Built target _controller_manager_msgs_generate_messages_check_deps_HardwareInterfaceResources
[  0%] Built target std_msgs_generate_messages_py
[  0%] Built target _controller_manager_msgs_generate_messages_check_deps_ControllerStatistics
[  0%] Built target _controller_manager_msgs_generate_messages_check_deps_ReloadControllerLibraries
[  0%] Built target std_msgs_generate_messages_eus
[  0%] Built target _multimaster_msgs_fkie_generate_messages_check_deps_SyncMasterInfo
[  0%] Built target _multimaster_msgs_fkie_generate_messages_check_deps_LinkStatesStamped
[  0%] Built target _multimaster_msgs_fkie_generate_messages_check_deps_ListDescription
[  0%] Built target _multimaster_msgs_fkie_generate_messages_check_deps_Task
[  0%] Built target _multimaster_msgs_fkie_generate_messages_check_deps_ListNodes
[  0%] Built target _multimaster_msgs_fkie_generate_messages_check_deps_Capability
[  0%] Built target _multimaster_msgs_fkie_generate_messages_check_deps_LoadLaunch
[  0%] Built target _multimaster_msgs_fkie_generate_messages_check_deps_GetSyncInfo
[  0%] Built target _multimaster_msgs_fkie_generate_messages_check_deps_MasterState
[  0%] Built target _multimaster_msgs_fkie_generate_messages_check_deps_SyncTopicInfo
[  0%] Built target _multimaster_msgs_fkie_generate_messages_check_deps_DiscoverMasters
[  0%] Built target _multimaster_msgs_fkie_generate_messages_check_deps_LinkState
[  0%] Generate version files
[  0%] Built target rosgraph_msgs_generate_messages_py
[  0%] Built target roscpp_generate_messages_lisp
[  0%] Built target TARGET
[  1%] Built target realtime_tools
[  1%] Built target _multimaster_msgs_fkie_generate_messages_check_deps_ROSMaster
[  1%] Built target roscpp_generate_messages_nodejs
[  1%] Built target roscpp_generate_messages_eus
[  1%] Built target _multimaster_msgs_fkie_generate_messages_check_deps_SyncServiceInfo
[  1%] Built target roscpp_generate_messages_cpp
[  1%] Built target rosgraph_msgs_generate_messages_nodejs
[  1%] Built target rosgraph_msgs_generate_messages_eus
[  1%] Built target rosgraph_msgs_generate_messages_cpp
[  1%] Built target roscpp_generate_messages_py
[  1%] Built target rosgraph_msgs_generate_messages_lisp
[  1%] Built target control_toolbox_gencfg
[  1%] Built target trajectory_msgs_generate_messages_cpp
[  1%] Built target _catkin_empty_exported_target
[  1%] Built target dynamic_reconfigure_generate_messages_eus
[  1%] Built target geometry_msgs_generate_messages_cpp
[  1%] Built target dynamic_reconfigure_generate_messages_cpp
[  1%] Built target _control_toolbox_generate_messages_check_deps_SetPidGains
[  1%] Built target trajectory_msgs_generate_messages_nodejs
[  1%] Built target trajectory_msgs_generate_messages_py
[  1%] Built target control_msgs_generate_messages_eus
[  1%] Built target geometry_msgs_generate_messages_nodejs
[  1%] Built target geometry_msgs_generate_messages_lisp
[  1%] Built target control_msgs_generate_messages_nodejs
[  1%] Built target control_msgs_generate_messages_cpp
[  1%] Built target actionlib_msgs_generate_messages_py
[  1%] Built target geometry_msgs_generate_messages_eus
[  1%] Built target trajectory_msgs_generate_messages_lisp
[  1%] Built target control_msgs_generate_messages_lisp
[  1%] Built target dynamic_reconfigure_generate_messages_lisp
[  1%] Built target actionlib_msgs_generate_messages_lisp
[  1%] Built target control_msgs_generate_messages_py
[  1%] Built target actionlib_msgs_generate_messages_cpp
[  1%] Built target actionlib_msgs_generate_messages_nodejs
[  1%] Built target dynamic_reconfigure_generate_messages_nodejs
[  1%] Built target dynamic_reconfigure_generate_messages_py
[  1%] Built target trajectory_msgs_generate_messages_eus
[  1%] Built target actionlib_msgs_generate_messages_eus
[  1%] Built target dynamic_reconfigure_gencfg
[  1%] Built target geometry_msgs_generate_messages_py
[  2%] Built target gtest
[  2%] Built target _gazebo_msgs_generate_messages_check_deps_SpawnModel
[  2%] Built target _driver_base_generate_messages_check_deps_ConfigString
[  2%] Built target _driver_base_generate_messages_check_deps_SensorLevels
[  2%] Built target _driver_base_generate_messages_check_deps_ConfigValue
[  2%] Built target _gazebo_msgs_generate_messages_check_deps_LinkState
[  2%] Built target _gazebo_msgs_generate_messages_check_deps_ContactState
[  2%] Built target _gazebo_msgs_generate_messages_check_deps_BodyRequest
[  2%] Built target _gazebo_msgs_generate_messages_check_deps_GetModelProperties
[  2%] Built target _gazebo_msgs_generate_messages_check_deps_GetModelState
[  2%] Built target _gazebo_msgs_generate_messages_check_deps_JointRequest
[  2%] Built target _gazebo_msgs_generate_messages_check_deps_ContactsState
[  2%] Built target _gazebo_msgs_generate_messages_check_deps_ModelState
[  2%] Built target _gazebo_msgs_generate_messages_check_deps_ODEPhysics
[  2%] Built target _gazebo_msgs_generate_messages_check_deps_SetModelConfiguration
[  2%] Built target _gazebo_msgs_generate_messages_check_deps_SetLinkState
[  2%] Built target _gazebo_msgs_generate_messages_check_deps_SetLinkProperties
[  2%] Built target _gazebo_msgs_generate_messages_check_deps_DeleteLight
[  2%] Built target _gazebo_msgs_generate_messages_check_deps_WorldState
[  2%] Built target _gazebo_msgs_generate_messages_check_deps_GetLightProperties
[  2%] Built target _gazebo_msgs_generate_messages_check_deps_SetJointTrajectory
[  2%] Built target _gazebo_msgs_generate_messages_check_deps_SetModelState
[  2%] Built target sensor_msgs_generate_messages_nodejs
[  2%] Built target _gazebo_msgs_generate_messages_check_deps_GetLinkState
[  2%] Built target _gazebo_msgs_generate_messages_check_deps_GetPhysicsProperties
[  2%] Built target _gazebo_msgs_generate_messages_check_deps_SetJointProperties
[  2%] Built target _gazebo_msgs_generate_messages_check_deps_ODEJointProperties
[  2%] Built target _gazebo_msgs_generate_messages_check_deps_GetWorldProperties
[  2%] Built target _gazebo_msgs_generate_messages_check_deps_GetJointProperties
[  2%] Built target _gazebo_msgs_generate_messages_check_deps_ApplyJointEffort
[  2%] Built target _gazebo_msgs_generate_messages_check_deps_DeleteModel
[  2%] Built target _gazebo_msgs_generate_messages_check_deps_GetLinkProperties
[  2%] Built target sensor_msgs_generate_messages_py
[  2%] Built target _gazebo_msgs_generate_messages_check_deps_SetLightProperties
[  2%] Built ...

(more)

edit retag flag offensive close merge delete

add a comment

answered 2019-01-23 06:49:42 -0500

gvdhoorn
86574 ●283 ●1432 ●1054 http://cor.tudelft.nl/

updated 2019-01-23 07:12:50 -0500

With C/C++ errors, it typically suffices to check the first error. In this case that would be:

In file included from /usr/include/c++/5/random:35:0,
                 from /usr/include/ignition/math2/ignition/math/Rand.hh:20,
                 from /usr/include/ignition/math2/ignition/math.hh:18,
                 from /usr/include/sdformat-4.0/sdf/Param.hh:34,
                 from /usr/include/sdformat-4.0/sdf/Element.hh:24,
                 from /usr/include/sdformat-4.0/sdf/sdf.hh:5,
                 from /usr/include/gazebo-7/gazebo/common/Plugin.hh:42,
                 from /home/metobom/m3_ws/src/evarobot_simulator/evarobot_gazebo/include/plugins/im_gazebo_ros_sonar.h:32,
                 from /home/metobom/m3_ws/src/evarobot_simulator/evarobot_gazebo/src/im_gazebo_ros_sonar.cpp:29:
/usr/include/c++/5/bits/c++0x_warning.h:32:2: error: #error This file requires compiler and library support for the ISO C++ 2011 standard. This support must be enabled with the -std=c++11 or -std=gnu++11 compiler options.
 #error This file requires compiler and library support \

which tells us that evarobot_simulator/evarobot_gazebo (or one of its direct dependencies) appears to require a C++11 enabled compiler.

As you tagged this kinetic, I assume you are running this on Ubuntu Xenial, which comes with GCC 5.4 by default, which afaik doesn't enable C++11 automatically.

Perhaps evarobot_simulator/evarobot_gazebo should enable C++11 in its build scripts (ie: CMakeLists.txt), but that would be something to ask the developers / maintainers.

Edit: according to this tutorial, the instructions are for Ubuntu Indigo:

These instructions will guide you through installing software and configuring your PC to communicate with the evarobot. You should install Ubuntu 14.04 operating system and ROS Indigo to your PC.

C++11 would not be enabled there by default either, but it could be that the requirement for C++11 comes from one of the dependencies of the evarobot packages, in which case changing to a newer platform could have introduced that without the evarobot packages themselves having changed.

Edit 2: and according to inomuh/evarobot_simulator#1, changes are needed to the various packages before they will build on Kinetic.

I'd ask the developers whether they support Ubuntu Xenial + ROS Kinetic.

edit flag offensive delete link

Comments

How can I compile with C++11? Is there any way to do it? And I use Ubuntu 16.04 LTS.

metobom ( 2019-01-23 07:06:39 -0500 )edit

I would expect the developers of the evarobot pkgs to have configured things correctly for you, so I would make sure you are using a supported platform first, before trying to change things.

re: Ubuntu 16.04: that is Ubuntu Xenial.