dev-ros:mavlink-gbp-release-2017.2.7-r1:20170310-162633.log

dev-ros:mavlink-gbp-release-2017.2.7-r1:20170310-162633.log (text/plain), 227.48 KB, created by Toralf Förster on 2017-03-10 18:38:17 UTC

 * Package:    dev-ros/mavlink-gbp-release-2017.2.7-r1
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux python_targets_python2_7 userland_GNU
 * FEATURES:   preserve-libs sandbox userpriv usersandbox
>>> Unpacking source...
>>> Unpacking mavlink-gbp-release-2017.2.7.tar.gz to /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work
>>> Source unpacked in /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work
>>> Preparing source in /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink ...
 * Applying gentoo.patch ...
 [ ok ]
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink ...
 * python2_7: running ros-catkin_src_configure_internal
>>> Working in BUILD_DIR: "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7"
cmake --no-warn-unused-cli -C /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/gentoo_common_config.cmake -G Unix Makefiles -DCMAKE_INSTALL_PREFIX=/usr -DCATKIN_ENABLE_TESTING=OFF -DCATKIN_BUILD_BINARY_PACKAGE=ON -DCATKIN_PREFIX_PATH=//usr -DPYTHON_EXECUTABLE=/usr/bin/python2.7 -DPYTHON_INSTALL_DIR=lib64/python2.7/site-packages -DCMAKE_BUILD_TYPE=Gentoo -DCMAKE_INSTALL_DO_STRIP=OFF -DCMAKE_USER_MAKE_RULES_OVERRIDE=/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/gentoo_rules.cmake -DCMAKE_TOOLCHAIN_FILE=/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/gentoo_toolchain.cmake  /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink
Not searching for unused variables given on the command line.
loading initial cache file /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/gentoo_common_config.cmake
-- Found PythonInterp: /usr/bin/python2.7 (found suitable version "2.7.13", minimum required is "2") 
-- Package version: 2017.2.7
-- processing v1.0: /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ASLUAV.xml
-- processing v1.0: /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ardupilotmega.xml
-- processing v1.0: /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/autoquad.xml
-- processing v1.0: /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml
-- processing v1.0: /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/matrixpilot.xml
-- processing v1.0: /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/paparazzi.xml
-- processing v1.0: /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/slugs.xml
-- processing v1.0: /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/standard.xml
-- processing v1.0: /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/uAvionix.xml
-- processing v1.0: /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ualberta.xml
-- processing v2.0: /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ASLUAV.xml
-- processing v2.0: /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ardupilotmega.xml
-- processing v2.0: /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/autoquad.xml
-- processing v2.0: /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml
-- processing v2.0: /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/matrixpilot.xml
-- processing v2.0: /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/paparazzi.xml
-- processing v2.0: /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/slugs.xml
-- processing v2.0: /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/standard.xml
-- processing v2.0: /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/uAvionix.xml
-- processing v2.0: /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ualberta.xml
-- <<< Gentoo configuration >>>
Build type      Gentoo
Install path    /usr
Compiler flags:
C               
C++             
Linker flags:
Executable      
Module          
Shared          

-- Configuring done
-- Generating done
-- Build files have been written to: /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7
>>> Source configured.
>>> Compiling source in /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink ...
 * python2_7: running cmake-utils_src_compile
>>> Working in BUILD_DIR: "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7"
make -j1 VERBOSE=1 
/usr/bin/cmake -H/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink -B/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 --check-build-system CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/progress.marks
make -f CMakeFiles/Makefile2 all
make[1]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
make -f CMakeFiles/ardupilotmega.xml-v1.0.dir/build.make CMakeFiles/ardupilotmega.xml-v1.0.dir/depend
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
cd /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/ardupilotmega.xml-v1.0.dir/DependInfo.cmake
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/ardupilotmega.xml-v1.0.dir/DependInfo.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/ardupilotmega.xml-v1.0.dir/depend.internal".
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/ardupilotmega.xml-v1.0.dir/depend.internal".
Scanning dependencies of target ardupilotmega.xml-v1.0
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
make -f CMakeFiles/ardupilotmega.xml-v1.0.dir/build.make CMakeFiles/ardupilotmega.xml-v1.0.dir/build
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[  3%] Generating include/v1.0/ardupilotmega/ardupilotmega.h
/usr/bin/env PYTHONPATH="/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink:" /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=1.0 --output=include/v1.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ardupilotmega.xml
 * ACCESS DENIED:  mkdir:        /root/cache
WARNING: Unable to load XML validator libraries. XML validation will not be performed
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ardupilotmega.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ardupilotmega.xml
Ignoring MAVLink2 message DEVICE_OP_READ
Ignoring MAVLink2 message DEVICE_OP_READ_REPLY
Ignoring MAVLink2 message DEVICE_OP_WRITE
Ignoring MAVLink2 message DEVICE_OP_WRITE_REPLY
Ignoring MAVLink2 message ADAP_TUNING
Note: message DATA64 is longer than 64 bytes long (74 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message DATA96 is longer than 64 bytes long (106 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message REMOTE_LOG_DATA_BLOCK is longer than 64 bytes long (214 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml
Ignoring MAVLink2 message SETUP_SIGNING
Ignoring MAVLink2 message BUTTON_CHANGE
Ignoring MAVLink2 message PLAY_TUNE
Ignoring MAVLink2 message CAMERA_INFORMATION
Ignoring MAVLink2 message CAMERA_SETTINGS
Ignoring MAVLink2 message STORAGE_INFORMATION
Ignoring MAVLink2 message CAMERA_CAPTURE_STATUS
Ignoring MAVLink2 message CAMERA_IMAGE_CAPTURED
Ignoring MAVLink2 message FLIGHT_INFORMATION
Ignoring MAVLink2 message MOUNT_ORIENTATION
Ignoring MAVLink2 message LOGGING_DATA
Ignoring MAVLink2 message LOGGING_DATA_ACKED
Ignoring MAVLink2 message LOGGING_ACK
Note: message GPS_STATUS is longer than 64 bytes long (109 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ATTITUDE_QUATERNION_COV is longer than 64 bytes long (80 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GLOBAL_POSITION_INT_COV is longer than 64 bytes long (189 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOCAL_POSITION_NED_COV is longer than 64 bytes long (233 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_ACTUATOR_CONTROLS is longer than 64 bytes long (89 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIGHRES_IMU is longer than 64 bytes long (70 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_SENSOR is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SIM_STATE is longer than 64 bytes long (92 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FILE_TRANSFER_PROTOCOL is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_STATE_QUATERNION is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOG_DATA is longer than 64 bytes long (105 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INJECT_DATA is longer than 64 bytes long (121 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_CONTROL is longer than 64 bytes long (87 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ENCAPSULATED_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message RESOURCE_REQUEST is longer than 64 bytes long (251 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FOLLOW_TARGET is longer than 64 bytes long (101 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CONTROL_SYSTEM_STATE is longer than 64 bytes long (108 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message AUTOPILOT_VERSION is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INPUT is longer than 64 bytes long (71 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_RTCM_DATA is longer than 64 bytes long (190 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message V2_EXTENSION is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/uAvionix.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/uAvionix.xml
Ignoring MAVLink2 message UAVIONIX_ADSB_OUT_CFG
Ignoring MAVLink2 message UAVIONIX_ADSB_OUT_DYNAMIC
Ignoring MAVLink2 message UAVIONIX_ADSB_TRANSCEIVER_HEALTH_REPORT
Merged enum MAV_CMD
Found 185 MAVLink message types in 3 XML files
Generating C implementation in directory include/v1.0/ardupilotmega
Generating C implementation in directory include/v1.0/common
Generating C implementation in directory include/v1.0/uAvionix
Copying fixed headers for protocol 1.0 to include/v1.0
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[  3%] Built target ardupilotmega.xml-v1.0
make -f CMakeFiles/uAvionix.xml-v1.0.dir/build.make CMakeFiles/uAvionix.xml-v1.0.dir/depend
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
cd /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/uAvionix.xml-v1.0.dir/DependInfo.cmake
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/uAvionix.xml-v1.0.dir/DependInfo.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/uAvionix.xml-v1.0.dir/depend.internal".
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/uAvionix.xml-v1.0.dir/depend.internal".
Scanning dependencies of target uAvionix.xml-v1.0
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
make -f CMakeFiles/uAvionix.xml-v1.0.dir/build.make CMakeFiles/uAvionix.xml-v1.0.dir/build
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
make[2]: Nothing to be done for 'CMakeFiles/uAvionix.xml-v1.0.dir/build'.
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[  6%] Built target uAvionix.xml-v1.0
make -f CMakeFiles/standard.xml-v1.0.dir/build.make CMakeFiles/standard.xml-v1.0.dir/depend
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
cd /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/standard.xml-v1.0.dir/DependInfo.cmake
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/standard.xml-v1.0.dir/DependInfo.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/standard.xml-v1.0.dir/depend.internal".
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/standard.xml-v1.0.dir/depend.internal".
Scanning dependencies of target standard.xml-v1.0
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
make -f CMakeFiles/standard.xml-v1.0.dir/build.make CMakeFiles/standard.xml-v1.0.dir/build
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[ 10%] Generating include/v1.0/standard/standard.h
/usr/bin/env PYTHONPATH="/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink:" /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=1.0 --output=include/v1.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/standard.xml
 * ACCESS DENIED:  mkdir:        /root/cache
WARNING: Unable to load XML validator libraries. XML validation will not be performed
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/standard.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/standard.xml
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml
Ignoring MAVLink2 message SETUP_SIGNING
Ignoring MAVLink2 message BUTTON_CHANGE
Ignoring MAVLink2 message PLAY_TUNE
Ignoring MAVLink2 message CAMERA_INFORMATION
Ignoring MAVLink2 message CAMERA_SETTINGS
Ignoring MAVLink2 message STORAGE_INFORMATION
Ignoring MAVLink2 message CAMERA_CAPTURE_STATUS
Ignoring MAVLink2 message CAMERA_IMAGE_CAPTURED
Ignoring MAVLink2 message FLIGHT_INFORMATION
Ignoring MAVLink2 message MOUNT_ORIENTATION
Ignoring MAVLink2 message LOGGING_DATA
Ignoring MAVLink2 message LOGGING_DATA_ACKED
Ignoring MAVLink2 message LOGGING_ACK
Note: message GPS_STATUS is longer than 64 bytes long (109 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ATTITUDE_QUATERNION_COV is longer than 64 bytes long (80 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GLOBAL_POSITION_INT_COV is longer than 64 bytes long (189 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOCAL_POSITION_NED_COV is longer than 64 bytes long (233 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_ACTUATOR_CONTROLS is longer than 64 bytes long (89 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIGHRES_IMU is longer than 64 bytes long (70 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_SENSOR is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SIM_STATE is longer than 64 bytes long (92 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FILE_TRANSFER_PROTOCOL is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_STATE_QUATERNION is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOG_DATA is longer than 64 bytes long (105 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INJECT_DATA is longer than 64 bytes long (121 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_CONTROL is longer than 64 bytes long (87 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ENCAPSULATED_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message RESOURCE_REQUEST is longer than 64 bytes long (251 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FOLLOW_TARGET is longer than 64 bytes long (101 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CONTROL_SYSTEM_STATE is longer than 64 bytes long (108 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message AUTOPILOT_VERSION is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INPUT is longer than 64 bytes long (71 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_RTCM_DATA is longer than 64 bytes long (190 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message V2_EXTENSION is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Found 136 MAVLink message types in 2 XML files
Generating C implementation in directory include/v1.0/standard
Generating C implementation in directory include/v1.0/common
Copying fixed headers for protocol 1.0 to include/v1.0
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[ 10%] Built target standard.xml-v1.0
make -f CMakeFiles/uAvionix.xml-v2.0.dir/build.make CMakeFiles/uAvionix.xml-v2.0.dir/depend
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
cd /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/uAvionix.xml-v2.0.dir/DependInfo.cmake
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/uAvionix.xml-v2.0.dir/DependInfo.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/uAvionix.xml-v2.0.dir/depend.internal".
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/uAvionix.xml-v2.0.dir/depend.internal".
Scanning dependencies of target uAvionix.xml-v2.0
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
make -f CMakeFiles/uAvionix.xml-v2.0.dir/build.make CMakeFiles/uAvionix.xml-v2.0.dir/build
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[ 13%] Generating uAvionix-v2.0-c.stamp
/usr/bin/env PYTHONPATH="/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink:" /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/uAvionix.xml
 * ACCESS DENIED:  mkdir:        /root/cache
WARNING: Unable to load XML validator libraries. XML validation will not be performed
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/uAvionix.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/uAvionix.xml
Found 3 MAVLink message types in 1 XML files
Generating C implementation in directory include/v2.0/uAvionix
Copying fixed headers for protocol 2.0 to include/v2.0
touch uAvionix-v2.0-c.stamp
[ 16%] Generating uAvionix-v2.0-cxx.stamp
/usr/bin/env PYTHONPATH="/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink:" /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C++11 --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/uAvionix.xml
 * ACCESS DENIED:  mkdir:        /root/cache
WARNING: Unable to load XML validator libraries. XML validation will not be performed
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/uAvionix.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/uAvionix.xml
Found 3 MAVLink message types in 1 XML files
Generating C++ implementation in directory include/v2.0/uAvionix
Copying fixed headers for protocol 2.0 to include/v2.0
touch uAvionix-v2.0-cxx.stamp
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[ 16%] Built target uAvionix.xml-v2.0
make -f CMakeFiles/matrixpilot.xml-v1.0.dir/build.make CMakeFiles/matrixpilot.xml-v1.0.dir/depend
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
cd /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/matrixpilot.xml-v1.0.dir/DependInfo.cmake
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/matrixpilot.xml-v1.0.dir/DependInfo.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/matrixpilot.xml-v1.0.dir/depend.internal".
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/matrixpilot.xml-v1.0.dir/depend.internal".
Scanning dependencies of target matrixpilot.xml-v1.0
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
make -f CMakeFiles/matrixpilot.xml-v1.0.dir/build.make CMakeFiles/matrixpilot.xml-v1.0.dir/build
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[ 20%] Generating include/v1.0/matrixpilot/matrixpilot.h
/usr/bin/env PYTHONPATH="/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink:" /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=1.0 --output=include/v1.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/matrixpilot.xml
 * ACCESS DENIED:  mkdir:        /root/cache
WARNING: Unable to load XML validator libraries. XML validation will not be performed
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/matrixpilot.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/matrixpilot.xml
Note: message FLEXIFUNCTION_BUFFER_FUNCTION is longer than 64 bytes long (66 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_UDB_EXTRA_F2_A is longer than 64 bytes long (69 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_UDB_EXTRA_F2_B is longer than 64 bytes long (116 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_UDB_EXTRA_F15 is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_UDB_EXTRA_F16 is longer than 64 bytes long (118 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml
Ignoring MAVLink2 message SETUP_SIGNING
Ignoring MAVLink2 message BUTTON_CHANGE
Ignoring MAVLink2 message PLAY_TUNE
Ignoring MAVLink2 message CAMERA_INFORMATION
Ignoring MAVLink2 message CAMERA_SETTINGS
Ignoring MAVLink2 message STORAGE_INFORMATION
Ignoring MAVLink2 message CAMERA_CAPTURE_STATUS
Ignoring MAVLink2 message CAMERA_IMAGE_CAPTURED
Ignoring MAVLink2 message FLIGHT_INFORMATION
Ignoring MAVLink2 message MOUNT_ORIENTATION
Ignoring MAVLink2 message LOGGING_DATA
Ignoring MAVLink2 message LOGGING_DATA_ACKED
Ignoring MAVLink2 message LOGGING_ACK
Note: message GPS_STATUS is longer than 64 bytes long (109 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ATTITUDE_QUATERNION_COV is longer than 64 bytes long (80 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GLOBAL_POSITION_INT_COV is longer than 64 bytes long (189 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOCAL_POSITION_NED_COV is longer than 64 bytes long (233 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_ACTUATOR_CONTROLS is longer than 64 bytes long (89 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIGHRES_IMU is longer than 64 bytes long (70 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_SENSOR is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SIM_STATE is longer than 64 bytes long (92 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FILE_TRANSFER_PROTOCOL is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_STATE_QUATERNION is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOG_DATA is longer than 64 bytes long (105 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INJECT_DATA is longer than 64 bytes long (121 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_CONTROL is longer than 64 bytes long (87 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ENCAPSULATED_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message RESOURCE_REQUEST is longer than 64 bytes long (251 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FOLLOW_TARGET is longer than 64 bytes long (101 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CONTROL_SYSTEM_STATE is longer than 64 bytes long (108 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message AUTOPILOT_VERSION is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INPUT is longer than 64 bytes long (71 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_RTCM_DATA is longer than 64 bytes long (190 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message V2_EXTENSION is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Merged enum MAV_CMD
Found 163 MAVLink message types in 2 XML files
Generating C implementation in directory include/v1.0/matrixpilot
Generating C implementation in directory include/v1.0/common
Copying fixed headers for protocol 1.0 to include/v1.0
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[ 20%] Built target matrixpilot.xml-v1.0
make -f CMakeFiles/standard.xml-v2.0.dir/build.make CMakeFiles/standard.xml-v2.0.dir/depend
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
cd /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/standard.xml-v2.0.dir/DependInfo.cmake
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/standard.xml-v2.0.dir/DependInfo.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/standard.xml-v2.0.dir/depend.internal".
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/standard.xml-v2.0.dir/depend.internal".
Scanning dependencies of target standard.xml-v2.0
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
make -f CMakeFiles/standard.xml-v2.0.dir/build.make CMakeFiles/standard.xml-v2.0.dir/build
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[ 23%] Generating standard-v2.0-c.stamp
/usr/bin/env PYTHONPATH="/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink:" /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/standard.xml
 * ACCESS DENIED:  mkdir:        /root/cache
WARNING: Unable to load XML validator libraries. XML validation will not be performed
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/standard.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/standard.xml
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml
Note: message GPS_STATUS is longer than 64 bytes long (109 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ATTITUDE_QUATERNION_COV is longer than 64 bytes long (80 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GLOBAL_POSITION_INT_COV is longer than 64 bytes long (189 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOCAL_POSITION_NED_COV is longer than 64 bytes long (233 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_ACTUATOR_CONTROLS is longer than 64 bytes long (89 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIGHRES_IMU is longer than 64 bytes long (70 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_SENSOR is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SIM_STATE is longer than 64 bytes long (92 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FILE_TRANSFER_PROTOCOL is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_STATE_QUATERNION is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOG_DATA is longer than 64 bytes long (105 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INJECT_DATA is longer than 64 bytes long (121 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_CONTROL is longer than 64 bytes long (87 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ENCAPSULATED_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message RESOURCE_REQUEST is longer than 64 bytes long (251 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FOLLOW_TARGET is longer than 64 bytes long (101 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CONTROL_SYSTEM_STATE is longer than 64 bytes long (108 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message AUTOPILOT_VERSION is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INPUT is longer than 64 bytes long (71 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_RTCM_DATA is longer than 64 bytes long (190 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message V2_EXTENSION is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_INFORMATION is longer than 64 bytes long (94 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_IMAGE_CAPTURED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA_ACKED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Found 149 MAVLink message types in 2 XML files
Generating C implementation in directory include/v2.0/standard
Generating C implementation in directory include/v2.0/common
Copying fixed headers for protocol 2.0 to include/v2.0
touch standard-v2.0-c.stamp
[ 26%] Generating standard-v2.0-cxx.stamp
/usr/bin/env PYTHONPATH="/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink:" /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C++11 --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/standard.xml
 * ACCESS DENIED:  mkdir:        /root/cache
WARNING: Unable to load XML validator libraries. XML validation will not be performed
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/standard.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/standard.xml
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml
Note: message GPS_STATUS is longer than 64 bytes long (109 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ATTITUDE_QUATERNION_COV is longer than 64 bytes long (80 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GLOBAL_POSITION_INT_COV is longer than 64 bytes long (189 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOCAL_POSITION_NED_COV is longer than 64 bytes long (233 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_ACTUATOR_CONTROLS is longer than 64 bytes long (89 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIGHRES_IMU is longer than 64 bytes long (70 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_SENSOR is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SIM_STATE is longer than 64 bytes long (92 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FILE_TRANSFER_PROTOCOL is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_STATE_QUATERNION is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOG_DATA is longer than 64 bytes long (105 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INJECT_DATA is longer than 64 bytes long (121 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_CONTROL is longer than 64 bytes long (87 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ENCAPSULATED_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message RESOURCE_REQUEST is longer than 64 bytes long (251 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FOLLOW_TARGET is longer than 64 bytes long (101 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CONTROL_SYSTEM_STATE is longer than 64 bytes long (108 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message AUTOPILOT_VERSION is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INPUT is longer than 64 bytes long (71 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_RTCM_DATA is longer than 64 bytes long (190 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message V2_EXTENSION is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_INFORMATION is longer than 64 bytes long (94 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_IMAGE_CAPTURED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA_ACKED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Found 149 MAVLink message types in 2 XML files
Generating C++ implementation in directory include/v2.0/standard
Generating C++ implementation in directory include/v2.0/common
Copying fixed headers for protocol 2.0 to include/v2.0
touch standard-v2.0-cxx.stamp
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[ 26%] Built target standard.xml-v2.0
make -f CMakeFiles/slugs.xml-v2.0.dir/build.make CMakeFiles/slugs.xml-v2.0.dir/depend
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
cd /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/slugs.xml-v2.0.dir/DependInfo.cmake
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/slugs.xml-v2.0.dir/DependInfo.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/slugs.xml-v2.0.dir/depend.internal".
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/slugs.xml-v2.0.dir/depend.internal".
Scanning dependencies of target slugs.xml-v2.0
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
make -f CMakeFiles/slugs.xml-v2.0.dir/build.make CMakeFiles/slugs.xml-v2.0.dir/build
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[ 30%] Generating slugs-v2.0-c.stamp
/usr/bin/env PYTHONPATH="/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink:" /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/slugs.xml
 * ACCESS DENIED:  mkdir:        /root/cache
WARNING: Unable to load XML validator libraries. XML validation will not be performed
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/slugs.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/slugs.xml
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml
Note: message GPS_STATUS is longer than 64 bytes long (109 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ATTITUDE_QUATERNION_COV is longer than 64 bytes long (80 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GLOBAL_POSITION_INT_COV is longer than 64 bytes long (189 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOCAL_POSITION_NED_COV is longer than 64 bytes long (233 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_ACTUATOR_CONTROLS is longer than 64 bytes long (89 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIGHRES_IMU is longer than 64 bytes long (70 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_SENSOR is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SIM_STATE is longer than 64 bytes long (92 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FILE_TRANSFER_PROTOCOL is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_STATE_QUATERNION is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOG_DATA is longer than 64 bytes long (105 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INJECT_DATA is longer than 64 bytes long (121 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_CONTROL is longer than 64 bytes long (87 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ENCAPSULATED_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message RESOURCE_REQUEST is longer than 64 bytes long (251 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FOLLOW_TARGET is longer than 64 bytes long (101 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CONTROL_SYSTEM_STATE is longer than 64 bytes long (108 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message AUTOPILOT_VERSION is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INPUT is longer than 64 bytes long (71 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_RTCM_DATA is longer than 64 bytes long (190 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message V2_EXTENSION is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_INFORMATION is longer than 64 bytes long (94 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_IMAGE_CAPTURED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA_ACKED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Merged enum MAV_CMD
Found 169 MAVLink message types in 2 XML files
Generating C implementation in directory include/v2.0/slugs
Generating C implementation in directory include/v2.0/common
Copying fixed headers for protocol 2.0 to include/v2.0
touch slugs-v2.0-c.stamp
[ 33%] Generating slugs-v2.0-cxx.stamp
/usr/bin/env PYTHONPATH="/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink:" /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C++11 --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/slugs.xml
 * ACCESS DENIED:  mkdir:        /root/cache
WARNING: Unable to load XML validator libraries. XML validation will not be performed
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/slugs.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/slugs.xml
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml
Note: message GPS_STATUS is longer than 64 bytes long (109 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ATTITUDE_QUATERNION_COV is longer than 64 bytes long (80 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GLOBAL_POSITION_INT_COV is longer than 64 bytes long (189 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOCAL_POSITION_NED_COV is longer than 64 bytes long (233 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_ACTUATOR_CONTROLS is longer than 64 bytes long (89 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIGHRES_IMU is longer than 64 bytes long (70 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_SENSOR is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SIM_STATE is longer than 64 bytes long (92 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FILE_TRANSFER_PROTOCOL is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_STATE_QUATERNION is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOG_DATA is longer than 64 bytes long (105 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INJECT_DATA is longer than 64 bytes long (121 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_CONTROL is longer than 64 bytes long (87 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ENCAPSULATED_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message RESOURCE_REQUEST is longer than 64 bytes long (251 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FOLLOW_TARGET is longer than 64 bytes long (101 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CONTROL_SYSTEM_STATE is longer than 64 bytes long (108 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message AUTOPILOT_VERSION is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INPUT is longer than 64 bytes long (71 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_RTCM_DATA is longer than 64 bytes long (190 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message V2_EXTENSION is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_INFORMATION is longer than 64 bytes long (94 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_IMAGE_CAPTURED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA_ACKED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Merged enum MAV_CMD
Found 169 MAVLink message types in 2 XML files
Generating C++ implementation in directory include/v2.0/slugs
Generating C++ implementation in directory include/v2.0/common
Copying fixed headers for protocol 2.0 to include/v2.0
touch slugs-v2.0-cxx.stamp
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[ 33%] Built target slugs.xml-v2.0
make -f CMakeFiles/ardupilotmega.xml-v2.0.dir/build.make CMakeFiles/ardupilotmega.xml-v2.0.dir/depend
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
cd /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/ardupilotmega.xml-v2.0.dir/DependInfo.cmake
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/ardupilotmega.xml-v2.0.dir/DependInfo.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/ardupilotmega.xml-v2.0.dir/depend.internal".
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/ardupilotmega.xml-v2.0.dir/depend.internal".
Scanning dependencies of target ardupilotmega.xml-v2.0
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
make -f CMakeFiles/ardupilotmega.xml-v2.0.dir/build.make CMakeFiles/ardupilotmega.xml-v2.0.dir/build
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[ 36%] Generating ardupilotmega-v2.0-c.stamp
/usr/bin/env PYTHONPATH="/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink:" /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ardupilotmega.xml
 * ACCESS DENIED:  mkdir:        /root/cache
WARNING: Unable to load XML validator libraries. XML validation will not be performed
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ardupilotmega.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ardupilotmega.xml
Note: message DATA64 is longer than 64 bytes long (74 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message DATA96 is longer than 64 bytes long (106 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message REMOTE_LOG_DATA_BLOCK is longer than 64 bytes long (214 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message DEVICE_OP_READ_REPLY is longer than 64 bytes long (143 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message DEVICE_OP_WRITE is longer than 64 bytes long (187 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml
Note: message GPS_STATUS is longer than 64 bytes long (109 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ATTITUDE_QUATERNION_COV is longer than 64 bytes long (80 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GLOBAL_POSITION_INT_COV is longer than 64 bytes long (189 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOCAL_POSITION_NED_COV is longer than 64 bytes long (233 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_ACTUATOR_CONTROLS is longer than 64 bytes long (89 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIGHRES_IMU is longer than 64 bytes long (70 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_SENSOR is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SIM_STATE is longer than 64 bytes long (92 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FILE_TRANSFER_PROTOCOL is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_STATE_QUATERNION is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOG_DATA is longer than 64 bytes long (105 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INJECT_DATA is longer than 64 bytes long (121 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_CONTROL is longer than 64 bytes long (87 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ENCAPSULATED_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message RESOURCE_REQUEST is longer than 64 bytes long (251 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FOLLOW_TARGET is longer than 64 bytes long (101 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CONTROL_SYSTEM_STATE is longer than 64 bytes long (108 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message AUTOPILOT_VERSION is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INPUT is longer than 64 bytes long (71 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_RTCM_DATA is longer than 64 bytes long (190 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message V2_EXTENSION is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_INFORMATION is longer than 64 bytes long (94 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_IMAGE_CAPTURED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA_ACKED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/uAvionix.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/uAvionix.xml
Merged enum MAV_CMD
Found 206 MAVLink message types in 3 XML files
Generating C implementation in directory include/v2.0/ardupilotmega
Generating C implementation in directory include/v2.0/common
Generating C implementation in directory include/v2.0/uAvionix
Copying fixed headers for protocol 2.0 to include/v2.0
touch ardupilotmega-v2.0-c.stamp
[ 40%] Generating ardupilotmega-v2.0-cxx.stamp
/usr/bin/env PYTHONPATH="/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink:" /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C++11 --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ardupilotmega.xml
 * ACCESS DENIED:  mkdir:        /root/cache
WARNING: Unable to load XML validator libraries. XML validation will not be performed
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ardupilotmega.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ardupilotmega.xml
Note: message DATA64 is longer than 64 bytes long (74 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message DATA96 is longer than 64 bytes long (106 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message REMOTE_LOG_DATA_BLOCK is longer than 64 bytes long (214 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message DEVICE_OP_READ_REPLY is longer than 64 bytes long (143 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message DEVICE_OP_WRITE is longer than 64 bytes long (187 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml
Note: message GPS_STATUS is longer than 64 bytes long (109 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ATTITUDE_QUATERNION_COV is longer than 64 bytes long (80 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GLOBAL_POSITION_INT_COV is longer than 64 bytes long (189 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOCAL_POSITION_NED_COV is longer than 64 bytes long (233 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_ACTUATOR_CONTROLS is longer than 64 bytes long (89 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIGHRES_IMU is longer than 64 bytes long (70 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_SENSOR is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SIM_STATE is longer than 64 bytes long (92 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FILE_TRANSFER_PROTOCOL is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_STATE_QUATERNION is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOG_DATA is longer than 64 bytes long (105 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INJECT_DATA is longer than 64 bytes long (121 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_CONTROL is longer than 64 bytes long (87 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ENCAPSULATED_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message RESOURCE_REQUEST is longer than 64 bytes long (251 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FOLLOW_TARGET is longer than 64 bytes long (101 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CONTROL_SYSTEM_STATE is longer than 64 bytes long (108 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message AUTOPILOT_VERSION is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INPUT is longer than 64 bytes long (71 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_RTCM_DATA is longer than 64 bytes long (190 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message V2_EXTENSION is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_INFORMATION is longer than 64 bytes long (94 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_IMAGE_CAPTURED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA_ACKED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/uAvionix.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/uAvionix.xml
Merged enum MAV_CMD
Found 206 MAVLink message types in 3 XML files
Generating C++ implementation in directory include/v2.0/ardupilotmega
Generating C++ implementation in directory include/v2.0/common
Generating C++ implementation in directory include/v2.0/uAvionix
Copying fixed headers for protocol 2.0 to include/v2.0
touch ardupilotmega-v2.0-cxx.stamp
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[ 40%] Built target ardupilotmega.xml-v2.0
make -f CMakeFiles/ASLUAV.xml-v2.0.dir/build.make CMakeFiles/ASLUAV.xml-v2.0.dir/depend
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
cd /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/ASLUAV.xml-v2.0.dir/DependInfo.cmake
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/ASLUAV.xml-v2.0.dir/DependInfo.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/ASLUAV.xml-v2.0.dir/depend.internal".
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/ASLUAV.xml-v2.0.dir/depend.internal".
Scanning dependencies of target ASLUAV.xml-v2.0
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
make -f CMakeFiles/ASLUAV.xml-v2.0.dir/build.make CMakeFiles/ASLUAV.xml-v2.0.dir/build
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[ 43%] Generating ASLUAV-v2.0-c.stamp
/usr/bin/env PYTHONPATH="/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink:" /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ASLUAV.xml
 * ACCESS DENIED:  mkdir:        /root/cache
WARNING: Unable to load XML validator libraries. XML validation will not be performed
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ASLUAV.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ASLUAV.xml
Note: message ASLCTRL_DATA is longer than 64 bytes long (106 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FW_SOARING_DATA is longer than 64 bytes long (110 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml
Note: message GPS_STATUS is longer than 64 bytes long (109 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ATTITUDE_QUATERNION_COV is longer than 64 bytes long (80 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GLOBAL_POSITION_INT_COV is longer than 64 bytes long (189 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOCAL_POSITION_NED_COV is longer than 64 bytes long (233 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_ACTUATOR_CONTROLS is longer than 64 bytes long (89 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIGHRES_IMU is longer than 64 bytes long (70 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_SENSOR is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SIM_STATE is longer than 64 bytes long (92 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FILE_TRANSFER_PROTOCOL is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_STATE_QUATERNION is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOG_DATA is longer than 64 bytes long (105 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INJECT_DATA is longer than 64 bytes long (121 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_CONTROL is longer than 64 bytes long (87 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ENCAPSULATED_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message RESOURCE_REQUEST is longer than 64 bytes long (251 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FOLLOW_TARGET is longer than 64 bytes long (101 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CONTROL_SYSTEM_STATE is longer than 64 bytes long (108 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message AUTOPILOT_VERSION is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INPUT is longer than 64 bytes long (71 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_RTCM_DATA is longer than 64 bytes long (190 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message V2_EXTENSION is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_INFORMATION is longer than 64 bytes long (94 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_IMAGE_CAPTURED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA_ACKED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Merged enum MAV_CMD
Found 161 MAVLink message types in 2 XML files
Generating C implementation in directory include/v2.0/ASLUAV
Generating C implementation in directory include/v2.0/common
Copying fixed headers for protocol 2.0 to include/v2.0
touch ASLUAV-v2.0-c.stamp
[ 46%] Generating ASLUAV-v2.0-cxx.stamp
/usr/bin/env PYTHONPATH="/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink:" /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C++11 --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ASLUAV.xml
 * ACCESS DENIED:  mkdir:        /root/cache
WARNING: Unable to load XML validator libraries. XML validation will not be performed
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ASLUAV.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ASLUAV.xml
Note: message ASLCTRL_DATA is longer than 64 bytes long (106 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FW_SOARING_DATA is longer than 64 bytes long (110 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml
Note: message GPS_STATUS is longer than 64 bytes long (109 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ATTITUDE_QUATERNION_COV is longer than 64 bytes long (80 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GLOBAL_POSITION_INT_COV is longer than 64 bytes long (189 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOCAL_POSITION_NED_COV is longer than 64 bytes long (233 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_ACTUATOR_CONTROLS is longer than 64 bytes long (89 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIGHRES_IMU is longer than 64 bytes long (70 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_SENSOR is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SIM_STATE is longer than 64 bytes long (92 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FILE_TRANSFER_PROTOCOL is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_STATE_QUATERNION is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOG_DATA is longer than 64 bytes long (105 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INJECT_DATA is longer than 64 bytes long (121 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_CONTROL is longer than 64 bytes long (87 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ENCAPSULATED_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message RESOURCE_REQUEST is longer than 64 bytes long (251 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FOLLOW_TARGET is longer than 64 bytes long (101 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CONTROL_SYSTEM_STATE is longer than 64 bytes long (108 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message AUTOPILOT_VERSION is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INPUT is longer than 64 bytes long (71 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_RTCM_DATA is longer than 64 bytes long (190 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message V2_EXTENSION is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_INFORMATION is longer than 64 bytes long (94 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_IMAGE_CAPTURED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA_ACKED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Merged enum MAV_CMD
Found 161 MAVLink message types in 2 XML files
Generating C++ implementation in directory include/v2.0/ASLUAV
Generating C++ implementation in directory include/v2.0/common
Copying fixed headers for protocol 2.0 to include/v2.0
touch ASLUAV-v2.0-cxx.stamp
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[ 46%] Built target ASLUAV.xml-v2.0
make -f CMakeFiles/paparazzi.xml-v2.0.dir/build.make CMakeFiles/paparazzi.xml-v2.0.dir/depend
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
cd /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/paparazzi.xml-v2.0.dir/DependInfo.cmake
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/paparazzi.xml-v2.0.dir/DependInfo.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/paparazzi.xml-v2.0.dir/depend.internal".
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/paparazzi.xml-v2.0.dir/depend.internal".
Scanning dependencies of target paparazzi.xml-v2.0
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
make -f CMakeFiles/paparazzi.xml-v2.0.dir/build.make CMakeFiles/paparazzi.xml-v2.0.dir/build
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[ 50%] Generating paparazzi-v2.0-c.stamp
/usr/bin/env PYTHONPATH="/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink:" /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/paparazzi.xml
 * ACCESS DENIED:  mkdir:        /root/cache
WARNING: Unable to load XML validator libraries. XML validation will not be performed
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/paparazzi.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/paparazzi.xml
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml
Note: message GPS_STATUS is longer than 64 bytes long (109 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ATTITUDE_QUATERNION_COV is longer than 64 bytes long (80 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GLOBAL_POSITION_INT_COV is longer than 64 bytes long (189 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOCAL_POSITION_NED_COV is longer than 64 bytes long (233 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_ACTUATOR_CONTROLS is longer than 64 bytes long (89 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIGHRES_IMU is longer than 64 bytes long (70 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_SENSOR is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SIM_STATE is longer than 64 bytes long (92 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FILE_TRANSFER_PROTOCOL is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_STATE_QUATERNION is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOG_DATA is longer than 64 bytes long (105 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INJECT_DATA is longer than 64 bytes long (121 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_CONTROL is longer than 64 bytes long (87 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ENCAPSULATED_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message RESOURCE_REQUEST is longer than 64 bytes long (251 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FOLLOW_TARGET is longer than 64 bytes long (101 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CONTROL_SYSTEM_STATE is longer than 64 bytes long (108 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message AUTOPILOT_VERSION is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INPUT is longer than 64 bytes long (71 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_RTCM_DATA is longer than 64 bytes long (190 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message V2_EXTENSION is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_INFORMATION is longer than 64 bytes long (94 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_IMAGE_CAPTURED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA_ACKED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Found 154 MAVLink message types in 2 XML files
Generating C implementation in directory include/v2.0/paparazzi
Generating C implementation in directory include/v2.0/common
Copying fixed headers for protocol 2.0 to include/v2.0
touch paparazzi-v2.0-c.stamp
[ 53%] Generating paparazzi-v2.0-cxx.stamp
/usr/bin/env PYTHONPATH="/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink:" /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C++11 --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/paparazzi.xml
 * ACCESS DENIED:  mkdir:        /root/cache
WARNING: Unable to load XML validator libraries. XML validation will not be performed
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/paparazzi.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/paparazzi.xml
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml
Note: message GPS_STATUS is longer than 64 bytes long (109 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ATTITUDE_QUATERNION_COV is longer than 64 bytes long (80 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GLOBAL_POSITION_INT_COV is longer than 64 bytes long (189 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOCAL_POSITION_NED_COV is longer than 64 bytes long (233 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_ACTUATOR_CONTROLS is longer than 64 bytes long (89 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIGHRES_IMU is longer than 64 bytes long (70 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_SENSOR is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SIM_STATE is longer than 64 bytes long (92 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FILE_TRANSFER_PROTOCOL is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_STATE_QUATERNION is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOG_DATA is longer than 64 bytes long (105 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INJECT_DATA is longer than 64 bytes long (121 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_CONTROL is longer than 64 bytes long (87 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ENCAPSULATED_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message RESOURCE_REQUEST is longer than 64 bytes long (251 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FOLLOW_TARGET is longer than 64 bytes long (101 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CONTROL_SYSTEM_STATE is longer than 64 bytes long (108 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message AUTOPILOT_VERSION is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INPUT is longer than 64 bytes long (71 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_RTCM_DATA is longer than 64 bytes long (190 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message V2_EXTENSION is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_INFORMATION is longer than 64 bytes long (94 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_IMAGE_CAPTURED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA_ACKED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Found 154 MAVLink message types in 2 XML files
Generating C++ implementation in directory include/v2.0/paparazzi
Generating C++ implementation in directory include/v2.0/common
Copying fixed headers for protocol 2.0 to include/v2.0
touch paparazzi-v2.0-cxx.stamp
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[ 53%] Built target paparazzi.xml-v2.0
make -f CMakeFiles/autoquad.xml-v2.0.dir/build.make CMakeFiles/autoquad.xml-v2.0.dir/depend
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
cd /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/autoquad.xml-v2.0.dir/DependInfo.cmake
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/autoquad.xml-v2.0.dir/DependInfo.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/autoquad.xml-v2.0.dir/depend.internal".
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/autoquad.xml-v2.0.dir/depend.internal".
Scanning dependencies of target autoquad.xml-v2.0
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
make -f CMakeFiles/autoquad.xml-v2.0.dir/build.make CMakeFiles/autoquad.xml-v2.0.dir/build
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[ 56%] Generating autoquad-v2.0-c.stamp
/usr/bin/env PYTHONPATH="/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink:" /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/autoquad.xml
 * ACCESS DENIED:  mkdir:        /root/cache
WARNING: Unable to load XML validator libraries. XML validation will not be performed
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/autoquad.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/autoquad.xml
Note: message AQ_TELEMETRY_F is longer than 64 bytes long (90 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml
Note: message GPS_STATUS is longer than 64 bytes long (109 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ATTITUDE_QUATERNION_COV is longer than 64 bytes long (80 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GLOBAL_POSITION_INT_COV is longer than 64 bytes long (189 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOCAL_POSITION_NED_COV is longer than 64 bytes long (233 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_ACTUATOR_CONTROLS is longer than 64 bytes long (89 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIGHRES_IMU is longer than 64 bytes long (70 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_SENSOR is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SIM_STATE is longer than 64 bytes long (92 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FILE_TRANSFER_PROTOCOL is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_STATE_QUATERNION is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOG_DATA is longer than 64 bytes long (105 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INJECT_DATA is longer than 64 bytes long (121 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_CONTROL is longer than 64 bytes long (87 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ENCAPSULATED_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message RESOURCE_REQUEST is longer than 64 bytes long (251 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FOLLOW_TARGET is longer than 64 bytes long (101 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CONTROL_SYSTEM_STATE is longer than 64 bytes long (108 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message AUTOPILOT_VERSION is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INPUT is longer than 64 bytes long (71 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_RTCM_DATA is longer than 64 bytes long (190 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message V2_EXTENSION is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_INFORMATION is longer than 64 bytes long (94 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_IMAGE_CAPTURED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA_ACKED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Merged enum MAV_CMD
Merged enum MAV_DATA_STREAM
Note: An enum value was auto-generated: AQ_MAVLINK_DEFS_VERSION_1 = 1
Note: An enum value was auto-generated: MAV_DATA_STREAM_PROPULSION = 13
Found 151 MAVLink message types in 2 XML files
Generating C implementation in directory include/v2.0/autoquad
Generating C implementation in directory include/v2.0/common
Copying fixed headers for protocol 2.0 to include/v2.0
touch autoquad-v2.0-c.stamp
[ 60%] Generating autoquad-v2.0-cxx.stamp
/usr/bin/env PYTHONPATH="/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink:" /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C++11 --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/autoquad.xml
 * ACCESS DENIED:  mkdir:        /root/cache
WARNING: Unable to load XML validator libraries. XML validation will not be performed
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/autoquad.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/autoquad.xml
Note: message AQ_TELEMETRY_F is longer than 64 bytes long (90 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml
Note: message GPS_STATUS is longer than 64 bytes long (109 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ATTITUDE_QUATERNION_COV is longer than 64 bytes long (80 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GLOBAL_POSITION_INT_COV is longer than 64 bytes long (189 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOCAL_POSITION_NED_COV is longer than 64 bytes long (233 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_ACTUATOR_CONTROLS is longer than 64 bytes long (89 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIGHRES_IMU is longer than 64 bytes long (70 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_SENSOR is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SIM_STATE is longer than 64 bytes long (92 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FILE_TRANSFER_PROTOCOL is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_STATE_QUATERNION is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOG_DATA is longer than 64 bytes long (105 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INJECT_DATA is longer than 64 bytes long (121 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_CONTROL is longer than 64 bytes long (87 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ENCAPSULATED_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message RESOURCE_REQUEST is longer than 64 bytes long (251 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FOLLOW_TARGET is longer than 64 bytes long (101 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CONTROL_SYSTEM_STATE is longer than 64 bytes long (108 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message AUTOPILOT_VERSION is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INPUT is longer than 64 bytes long (71 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_RTCM_DATA is longer than 64 bytes long (190 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message V2_EXTENSION is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_INFORMATION is longer than 64 bytes long (94 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_IMAGE_CAPTURED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA_ACKED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Merged enum MAV_CMD
Merged enum MAV_DATA_STREAM
Note: An enum value was auto-generated: AQ_MAVLINK_DEFS_VERSION_1 = 1
Note: An enum value was auto-generated: MAV_DATA_STREAM_PROPULSION = 13
Found 151 MAVLink message types in 2 XML files
Generating C++ implementation in directory include/v2.0/autoquad
Generating C++ implementation in directory include/v2.0/common
Copying fixed headers for protocol 2.0 to include/v2.0
touch autoquad-v2.0-cxx.stamp
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[ 60%] Built target autoquad.xml-v2.0
make -f CMakeFiles/matrixpilot.xml-v2.0.dir/build.make CMakeFiles/matrixpilot.xml-v2.0.dir/depend
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
cd /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/matrixpilot.xml-v2.0.dir/DependInfo.cmake
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/matrixpilot.xml-v2.0.dir/DependInfo.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/matrixpilot.xml-v2.0.dir/depend.internal".
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/matrixpilot.xml-v2.0.dir/depend.internal".
Scanning dependencies of target matrixpilot.xml-v2.0
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
make -f CMakeFiles/matrixpilot.xml-v2.0.dir/build.make CMakeFiles/matrixpilot.xml-v2.0.dir/build
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[ 63%] Generating matrixpilot-v2.0-c.stamp
/usr/bin/env PYTHONPATH="/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink:" /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/matrixpilot.xml
 * ACCESS DENIED:  mkdir:        /root/cache
WARNING: Unable to load XML validator libraries. XML validation will not be performed
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/matrixpilot.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/matrixpilot.xml
Note: message FLEXIFUNCTION_BUFFER_FUNCTION is longer than 64 bytes long (66 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_UDB_EXTRA_F2_A is longer than 64 bytes long (69 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_UDB_EXTRA_F2_B is longer than 64 bytes long (116 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_UDB_EXTRA_F15 is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_UDB_EXTRA_F16 is longer than 64 bytes long (118 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml
Note: message GPS_STATUS is longer than 64 bytes long (109 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ATTITUDE_QUATERNION_COV is longer than 64 bytes long (80 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GLOBAL_POSITION_INT_COV is longer than 64 bytes long (189 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOCAL_POSITION_NED_COV is longer than 64 bytes long (233 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_ACTUATOR_CONTROLS is longer than 64 bytes long (89 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIGHRES_IMU is longer than 64 bytes long (70 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_SENSOR is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SIM_STATE is longer than 64 bytes long (92 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FILE_TRANSFER_PROTOCOL is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_STATE_QUATERNION is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOG_DATA is longer than 64 bytes long (105 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INJECT_DATA is longer than 64 bytes long (121 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_CONTROL is longer than 64 bytes long (87 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ENCAPSULATED_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message RESOURCE_REQUEST is longer than 64 bytes long (251 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FOLLOW_TARGET is longer than 64 bytes long (101 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CONTROL_SYSTEM_STATE is longer than 64 bytes long (108 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message AUTOPILOT_VERSION is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INPUT is longer than 64 bytes long (71 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_RTCM_DATA is longer than 64 bytes long (190 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message V2_EXTENSION is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_INFORMATION is longer than 64 bytes long (94 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_IMAGE_CAPTURED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA_ACKED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Merged enum MAV_CMD
Found 176 MAVLink message types in 2 XML files
Generating C implementation in directory include/v2.0/matrixpilot
Generating C implementation in directory include/v2.0/common
Copying fixed headers for protocol 2.0 to include/v2.0
touch matrixpilot-v2.0-c.stamp
[ 66%] Generating matrixpilot-v2.0-cxx.stamp
/usr/bin/env PYTHONPATH="/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink:" /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C++11 --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/matrixpilot.xml
 * ACCESS DENIED:  mkdir:        /root/cache
WARNING: Unable to load XML validator libraries. XML validation will not be performed
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/matrixpilot.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/matrixpilot.xml
Note: message FLEXIFUNCTION_BUFFER_FUNCTION is longer than 64 bytes long (66 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_UDB_EXTRA_F2_A is longer than 64 bytes long (69 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_UDB_EXTRA_F2_B is longer than 64 bytes long (116 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_UDB_EXTRA_F15 is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_UDB_EXTRA_F16 is longer than 64 bytes long (118 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml
Note: message GPS_STATUS is longer than 64 bytes long (109 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ATTITUDE_QUATERNION_COV is longer than 64 bytes long (80 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GLOBAL_POSITION_INT_COV is longer than 64 bytes long (189 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOCAL_POSITION_NED_COV is longer than 64 bytes long (233 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_ACTUATOR_CONTROLS is longer than 64 bytes long (89 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIGHRES_IMU is longer than 64 bytes long (70 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_SENSOR is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SIM_STATE is longer than 64 bytes long (92 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FILE_TRANSFER_PROTOCOL is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_STATE_QUATERNION is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOG_DATA is longer than 64 bytes long (105 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INJECT_DATA is longer than 64 bytes long (121 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_CONTROL is longer than 64 bytes long (87 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ENCAPSULATED_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message RESOURCE_REQUEST is longer than 64 bytes long (251 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FOLLOW_TARGET is longer than 64 bytes long (101 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CONTROL_SYSTEM_STATE is longer than 64 bytes long (108 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message AUTOPILOT_VERSION is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INPUT is longer than 64 bytes long (71 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_RTCM_DATA is longer than 64 bytes long (190 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message V2_EXTENSION is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_INFORMATION is longer than 64 bytes long (94 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_IMAGE_CAPTURED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA_ACKED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Merged enum MAV_CMD
Found 176 MAVLink message types in 2 XML files
Generating C++ implementation in directory include/v2.0/matrixpilot
Generating C++ implementation in directory include/v2.0/common
Copying fixed headers for protocol 2.0 to include/v2.0
touch matrixpilot-v2.0-cxx.stamp
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[ 66%] Built target matrixpilot.xml-v2.0
make -f CMakeFiles/ualberta.xml-v2.0.dir/build.make CMakeFiles/ualberta.xml-v2.0.dir/depend
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
cd /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/ualberta.xml-v2.0.dir/DependInfo.cmake
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/ualberta.xml-v2.0.dir/DependInfo.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/ualberta.xml-v2.0.dir/depend.internal".
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/ualberta.xml-v2.0.dir/depend.internal".
Scanning dependencies of target ualberta.xml-v2.0
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
make -f CMakeFiles/ualberta.xml-v2.0.dir/build.make CMakeFiles/ualberta.xml-v2.0.dir/build
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[ 70%] Generating ualberta-v2.0-c.stamp
/usr/bin/env PYTHONPATH="/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink:" /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ualberta.xml
 * ACCESS DENIED:  mkdir:        /root/cache
WARNING: Unable to load XML validator libraries. XML validation will not be performed
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ualberta.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ualberta.xml
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml
Note: message GPS_STATUS is longer than 64 bytes long (109 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ATTITUDE_QUATERNION_COV is longer than 64 bytes long (80 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GLOBAL_POSITION_INT_COV is longer than 64 bytes long (189 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOCAL_POSITION_NED_COV is longer than 64 bytes long (233 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_ACTUATOR_CONTROLS is longer than 64 bytes long (89 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIGHRES_IMU is longer than 64 bytes long (70 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_SENSOR is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SIM_STATE is longer than 64 bytes long (92 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FILE_TRANSFER_PROTOCOL is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_STATE_QUATERNION is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOG_DATA is longer than 64 bytes long (105 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INJECT_DATA is longer than 64 bytes long (121 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_CONTROL is longer than 64 bytes long (87 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ENCAPSULATED_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message RESOURCE_REQUEST is longer than 64 bytes long (251 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FOLLOW_TARGET is longer than 64 bytes long (101 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CONTROL_SYSTEM_STATE is longer than 64 bytes long (108 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message AUTOPILOT_VERSION is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INPUT is longer than 64 bytes long (71 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_RTCM_DATA is longer than 64 bytes long (190 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message V2_EXTENSION is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_INFORMATION is longer than 64 bytes long (94 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_IMAGE_CAPTURED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA_ACKED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: An enum value was auto-generated: MODE_MANUAL_DIRECT = 1
Note: An enum value was auto-generated: MODE_MANUAL_SCALED = 2
Note: An enum value was auto-generated: MODE_AUTO_PID_ATT = 3
Note: An enum value was auto-generated: MODE_AUTO_PID_VEL = 4
Note: An enum value was auto-generated: MODE_AUTO_PID_POS = 5
Note: An enum value was auto-generated: NAV_AHRS_INIT = 1
Note: An enum value was auto-generated: NAV_AHRS = 2
Note: An enum value was auto-generated: NAV_INS_GPS_INIT = 3
Note: An enum value was auto-generated: NAV_INS_GPS = 4
Note: An enum value was auto-generated: PILOT_MANUAL = 1
Note: An enum value was auto-generated: PILOT_AUTO = 2
Note: An enum value was auto-generated: PILOT_ROTO = 3
Found 152 MAVLink message types in 2 XML files
Generating C implementation in directory include/v2.0/ualberta
Generating C implementation in directory include/v2.0/common
Copying fixed headers for protocol 2.0 to include/v2.0
touch ualberta-v2.0-c.stamp
[ 73%] Generating ualberta-v2.0-cxx.stamp
/usr/bin/env PYTHONPATH="/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink:" /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C++11 --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ualberta.xml
 * ACCESS DENIED:  mkdir:        /root/cache
WARNING: Unable to load XML validator libraries. XML validation will not be performed
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ualberta.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ualberta.xml
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml
Note: message GPS_STATUS is longer than 64 bytes long (109 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ATTITUDE_QUATERNION_COV is longer than 64 bytes long (80 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GLOBAL_POSITION_INT_COV is longer than 64 bytes long (189 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOCAL_POSITION_NED_COV is longer than 64 bytes long (233 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_ACTUATOR_CONTROLS is longer than 64 bytes long (89 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIGHRES_IMU is longer than 64 bytes long (70 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_SENSOR is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SIM_STATE is longer than 64 bytes long (92 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FILE_TRANSFER_PROTOCOL is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_STATE_QUATERNION is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOG_DATA is longer than 64 bytes long (105 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INJECT_DATA is longer than 64 bytes long (121 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_CONTROL is longer than 64 bytes long (87 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ENCAPSULATED_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message RESOURCE_REQUEST is longer than 64 bytes long (251 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FOLLOW_TARGET is longer than 64 bytes long (101 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CONTROL_SYSTEM_STATE is longer than 64 bytes long (108 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message AUTOPILOT_VERSION is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INPUT is longer than 64 bytes long (71 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_RTCM_DATA is longer than 64 bytes long (190 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message V2_EXTENSION is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_INFORMATION is longer than 64 bytes long (94 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_IMAGE_CAPTURED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA_ACKED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: An enum value was auto-generated: MODE_MANUAL_DIRECT = 1
Note: An enum value was auto-generated: MODE_MANUAL_SCALED = 2
Note: An enum value was auto-generated: MODE_AUTO_PID_ATT = 3
Note: An enum value was auto-generated: MODE_AUTO_PID_VEL = 4
Note: An enum value was auto-generated: MODE_AUTO_PID_POS = 5
Note: An enum value was auto-generated: NAV_AHRS_INIT = 1
Note: An enum value was auto-generated: NAV_AHRS = 2
Note: An enum value was auto-generated: NAV_INS_GPS_INIT = 3
Note: An enum value was auto-generated: NAV_INS_GPS = 4
Note: An enum value was auto-generated: PILOT_MANUAL = 1
Note: An enum value was auto-generated: PILOT_AUTO = 2
Note: An enum value was auto-generated: PILOT_ROTO = 3
Found 152 MAVLink message types in 2 XML files
Generating C++ implementation in directory include/v2.0/ualberta
Generating C++ implementation in directory include/v2.0/common
Copying fixed headers for protocol 2.0 to include/v2.0
touch ualberta-v2.0-cxx.stamp
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[ 73%] Built target ualberta.xml-v2.0
make -f CMakeFiles/common.xml-v2.0.dir/build.make CMakeFiles/common.xml-v2.0.dir/depend
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
cd /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/common.xml-v2.0.dir/DependInfo.cmake
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/common.xml-v2.0.dir/DependInfo.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/common.xml-v2.0.dir/depend.internal".
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/common.xml-v2.0.dir/depend.internal".
Scanning dependencies of target common.xml-v2.0
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
make -f CMakeFiles/common.xml-v2.0.dir/build.make CMakeFiles/common.xml-v2.0.dir/build
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[ 76%] Generating common-v2.0-c.stamp
/usr/bin/env PYTHONPATH="/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink:" /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml
 * ACCESS DENIED:  mkdir:        /root/cache
WARNING: Unable to load XML validator libraries. XML validation will not be performed
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml
Note: message GPS_STATUS is longer than 64 bytes long (109 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ATTITUDE_QUATERNION_COV is longer than 64 bytes long (80 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GLOBAL_POSITION_INT_COV is longer than 64 bytes long (189 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOCAL_POSITION_NED_COV is longer than 64 bytes long (233 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_ACTUATOR_CONTROLS is longer than 64 bytes long (89 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIGHRES_IMU is longer than 64 bytes long (70 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_SENSOR is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SIM_STATE is longer than 64 bytes long (92 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FILE_TRANSFER_PROTOCOL is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_STATE_QUATERNION is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOG_DATA is longer than 64 bytes long (105 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INJECT_DATA is longer than 64 bytes long (121 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_CONTROL is longer than 64 bytes long (87 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ENCAPSULATED_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message RESOURCE_REQUEST is longer than 64 bytes long (251 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FOLLOW_TARGET is longer than 64 bytes long (101 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CONTROL_SYSTEM_STATE is longer than 64 bytes long (108 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message AUTOPILOT_VERSION is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INPUT is longer than 64 bytes long (71 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_RTCM_DATA is longer than 64 bytes long (190 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message V2_EXTENSION is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_INFORMATION is longer than 64 bytes long (94 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_IMAGE_CAPTURED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA_ACKED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Found 149 MAVLink message types in 1 XML files
Generating C implementation in directory include/v2.0/common
Copying fixed headers for protocol 2.0 to include/v2.0
touch common-v2.0-c.stamp
[ 80%] Generating common-v2.0-cxx.stamp
/usr/bin/env PYTHONPATH="/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink:" /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C++11 --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml
 * ACCESS DENIED:  mkdir:        /root/cache
WARNING: Unable to load XML validator libraries. XML validation will not be performed
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml
Note: message GPS_STATUS is longer than 64 bytes long (109 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ATTITUDE_QUATERNION_COV is longer than 64 bytes long (80 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GLOBAL_POSITION_INT_COV is longer than 64 bytes long (189 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOCAL_POSITION_NED_COV is longer than 64 bytes long (233 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_ACTUATOR_CONTROLS is longer than 64 bytes long (89 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIGHRES_IMU is longer than 64 bytes long (70 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_SENSOR is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SIM_STATE is longer than 64 bytes long (92 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FILE_TRANSFER_PROTOCOL is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_STATE_QUATERNION is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOG_DATA is longer than 64 bytes long (105 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INJECT_DATA is longer than 64 bytes long (121 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_CONTROL is longer than 64 bytes long (87 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ENCAPSULATED_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message RESOURCE_REQUEST is longer than 64 bytes long (251 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FOLLOW_TARGET is longer than 64 bytes long (101 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CONTROL_SYSTEM_STATE is longer than 64 bytes long (108 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message AUTOPILOT_VERSION is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INPUT is longer than 64 bytes long (71 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_RTCM_DATA is longer than 64 bytes long (190 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message V2_EXTENSION is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_INFORMATION is longer than 64 bytes long (94 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_IMAGE_CAPTURED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA_ACKED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Found 149 MAVLink message types in 1 XML files
Generating C++ implementation in directory include/v2.0/common
Copying fixed headers for protocol 2.0 to include/v2.0
touch common-v2.0-cxx.stamp
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[ 80%] Built target common.xml-v2.0
make -f CMakeFiles/paparazzi.xml-v1.0.dir/build.make CMakeFiles/paparazzi.xml-v1.0.dir/depend
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
cd /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/paparazzi.xml-v1.0.dir/DependInfo.cmake
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/paparazzi.xml-v1.0.dir/DependInfo.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/paparazzi.xml-v1.0.dir/depend.internal".
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/paparazzi.xml-v1.0.dir/depend.internal".
Scanning dependencies of target paparazzi.xml-v1.0
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
make -f CMakeFiles/paparazzi.xml-v1.0.dir/build.make CMakeFiles/paparazzi.xml-v1.0.dir/build
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[ 83%] Generating include/v1.0/paparazzi/paparazzi.h
/usr/bin/env PYTHONPATH="/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink:" /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=1.0 --output=include/v1.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/paparazzi.xml
 * ACCESS DENIED:  mkdir:        /root/cache
WARNING: Unable to load XML validator libraries. XML validation will not be performed
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/paparazzi.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/paparazzi.xml
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml
Ignoring MAVLink2 message SETUP_SIGNING
Ignoring MAVLink2 message BUTTON_CHANGE
Ignoring MAVLink2 message PLAY_TUNE
Ignoring MAVLink2 message CAMERA_INFORMATION
Ignoring MAVLink2 message CAMERA_SETTINGS
Ignoring MAVLink2 message STORAGE_INFORMATION
Ignoring MAVLink2 message CAMERA_CAPTURE_STATUS
Ignoring MAVLink2 message CAMERA_IMAGE_CAPTURED
Ignoring MAVLink2 message FLIGHT_INFORMATION
Ignoring MAVLink2 message MOUNT_ORIENTATION
Ignoring MAVLink2 message LOGGING_DATA
Ignoring MAVLink2 message LOGGING_DATA_ACKED
Ignoring MAVLink2 message LOGGING_ACK
Note: message GPS_STATUS is longer than 64 bytes long (109 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ATTITUDE_QUATERNION_COV is longer than 64 bytes long (80 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GLOBAL_POSITION_INT_COV is longer than 64 bytes long (189 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOCAL_POSITION_NED_COV is longer than 64 bytes long (233 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_ACTUATOR_CONTROLS is longer than 64 bytes long (89 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIGHRES_IMU is longer than 64 bytes long (70 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_SENSOR is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SIM_STATE is longer than 64 bytes long (92 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FILE_TRANSFER_PROTOCOL is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_STATE_QUATERNION is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOG_DATA is longer than 64 bytes long (105 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INJECT_DATA is longer than 64 bytes long (121 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_CONTROL is longer than 64 bytes long (87 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ENCAPSULATED_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message RESOURCE_REQUEST is longer than 64 bytes long (251 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FOLLOW_TARGET is longer than 64 bytes long (101 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CONTROL_SYSTEM_STATE is longer than 64 bytes long (108 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message AUTOPILOT_VERSION is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INPUT is longer than 64 bytes long (71 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_RTCM_DATA is longer than 64 bytes long (190 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message V2_EXTENSION is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Found 141 MAVLink message types in 2 XML files
Generating C implementation in directory include/v1.0/paparazzi
Generating C implementation in directory include/v1.0/common
Copying fixed headers for protocol 1.0 to include/v1.0
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[ 83%] Built target paparazzi.xml-v1.0
make -f CMakeFiles/slugs.xml-v1.0.dir/build.make CMakeFiles/slugs.xml-v1.0.dir/depend
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
cd /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/slugs.xml-v1.0.dir/DependInfo.cmake
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/slugs.xml-v1.0.dir/DependInfo.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/slugs.xml-v1.0.dir/depend.internal".
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/slugs.xml-v1.0.dir/depend.internal".
Scanning dependencies of target slugs.xml-v1.0
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
make -f CMakeFiles/slugs.xml-v1.0.dir/build.make CMakeFiles/slugs.xml-v1.0.dir/build
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[ 86%] Generating include/v1.0/slugs/slugs.h
/usr/bin/env PYTHONPATH="/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink:" /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=1.0 --output=include/v1.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/slugs.xml
 * ACCESS DENIED:  mkdir:        /root/cache
WARNING: Unable to load XML validator libraries. XML validation will not be performed
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/slugs.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/slugs.xml
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml
Ignoring MAVLink2 message SETUP_SIGNING
Ignoring MAVLink2 message BUTTON_CHANGE
Ignoring MAVLink2 message PLAY_TUNE
Ignoring MAVLink2 message CAMERA_INFORMATION
Ignoring MAVLink2 message CAMERA_SETTINGS
Ignoring MAVLink2 message STORAGE_INFORMATION
Ignoring MAVLink2 message CAMERA_CAPTURE_STATUS
Ignoring MAVLink2 message CAMERA_IMAGE_CAPTURED
Ignoring MAVLink2 message FLIGHT_INFORMATION
Ignoring MAVLink2 message MOUNT_ORIENTATION
Ignoring MAVLink2 message LOGGING_DATA
Ignoring MAVLink2 message LOGGING_DATA_ACKED
Ignoring MAVLink2 message LOGGING_ACK
Note: message GPS_STATUS is longer than 64 bytes long (109 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ATTITUDE_QUATERNION_COV is longer than 64 bytes long (80 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GLOBAL_POSITION_INT_COV is longer than 64 bytes long (189 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOCAL_POSITION_NED_COV is longer than 64 bytes long (233 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_ACTUATOR_CONTROLS is longer than 64 bytes long (89 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIGHRES_IMU is longer than 64 bytes long (70 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_SENSOR is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SIM_STATE is longer than 64 bytes long (92 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FILE_TRANSFER_PROTOCOL is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_STATE_QUATERNION is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOG_DATA is longer than 64 bytes long (105 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INJECT_DATA is longer than 64 bytes long (121 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_CONTROL is longer than 64 bytes long (87 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ENCAPSULATED_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message RESOURCE_REQUEST is longer than 64 bytes long (251 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FOLLOW_TARGET is longer than 64 bytes long (101 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CONTROL_SYSTEM_STATE is longer than 64 bytes long (108 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message AUTOPILOT_VERSION is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INPUT is longer than 64 bytes long (71 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_RTCM_DATA is longer than 64 bytes long (190 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message V2_EXTENSION is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Merged enum MAV_CMD
Found 156 MAVLink message types in 2 XML files
Generating C implementation in directory include/v1.0/slugs
Generating C implementation in directory include/v1.0/common
Copying fixed headers for protocol 1.0 to include/v1.0
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[ 86%] Built target slugs.xml-v1.0
make -f CMakeFiles/ASLUAV.xml-v1.0.dir/build.make CMakeFiles/ASLUAV.xml-v1.0.dir/depend
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
cd /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/ASLUAV.xml-v1.0.dir/DependInfo.cmake
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/ASLUAV.xml-v1.0.dir/DependInfo.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/ASLUAV.xml-v1.0.dir/depend.internal".
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/ASLUAV.xml-v1.0.dir/depend.internal".
Scanning dependencies of target ASLUAV.xml-v1.0
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
make -f CMakeFiles/ASLUAV.xml-v1.0.dir/build.make CMakeFiles/ASLUAV.xml-v1.0.dir/build
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[ 90%] Generating include/v1.0/ASLUAV/ASLUAV.h
/usr/bin/env PYTHONPATH="/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink:" /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=1.0 --output=include/v1.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ASLUAV.xml
 * ACCESS DENIED:  mkdir:        /root/cache
WARNING: Unable to load XML validator libraries. XML validation will not be performed
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ASLUAV.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ASLUAV.xml
Note: message ASLCTRL_DATA is longer than 64 bytes long (106 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FW_SOARING_DATA is longer than 64 bytes long (110 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml
Ignoring MAVLink2 message SETUP_SIGNING
Ignoring MAVLink2 message BUTTON_CHANGE
Ignoring MAVLink2 message PLAY_TUNE
Ignoring MAVLink2 message CAMERA_INFORMATION
Ignoring MAVLink2 message CAMERA_SETTINGS
Ignoring MAVLink2 message STORAGE_INFORMATION
Ignoring MAVLink2 message CAMERA_CAPTURE_STATUS
Ignoring MAVLink2 message CAMERA_IMAGE_CAPTURED
Ignoring MAVLink2 message FLIGHT_INFORMATION
Ignoring MAVLink2 message MOUNT_ORIENTATION
Ignoring MAVLink2 message LOGGING_DATA
Ignoring MAVLink2 message LOGGING_DATA_ACKED
Ignoring MAVLink2 message LOGGING_ACK
Note: message GPS_STATUS is longer than 64 bytes long (109 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ATTITUDE_QUATERNION_COV is longer than 64 bytes long (80 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GLOBAL_POSITION_INT_COV is longer than 64 bytes long (189 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOCAL_POSITION_NED_COV is longer than 64 bytes long (233 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_ACTUATOR_CONTROLS is longer than 64 bytes long (89 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIGHRES_IMU is longer than 64 bytes long (70 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_SENSOR is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SIM_STATE is longer than 64 bytes long (92 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FILE_TRANSFER_PROTOCOL is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_STATE_QUATERNION is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOG_DATA is longer than 64 bytes long (105 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INJECT_DATA is longer than 64 bytes long (121 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_CONTROL is longer than 64 bytes long (87 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ENCAPSULATED_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message RESOURCE_REQUEST is longer than 64 bytes long (251 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FOLLOW_TARGET is longer than 64 bytes long (101 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CONTROL_SYSTEM_STATE is longer than 64 bytes long (108 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message AUTOPILOT_VERSION is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INPUT is longer than 64 bytes long (71 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_RTCM_DATA is longer than 64 bytes long (190 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message V2_EXTENSION is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Merged enum MAV_CMD
Found 148 MAVLink message types in 2 XML files
Generating C implementation in directory include/v1.0/ASLUAV
Generating C implementation in directory include/v1.0/common
Copying fixed headers for protocol 1.0 to include/v1.0
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[ 90%] Built target ASLUAV.xml-v1.0
make -f CMakeFiles/autoquad.xml-v1.0.dir/build.make CMakeFiles/autoquad.xml-v1.0.dir/depend
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
cd /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/autoquad.xml-v1.0.dir/DependInfo.cmake
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/autoquad.xml-v1.0.dir/DependInfo.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/autoquad.xml-v1.0.dir/depend.internal".
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/autoquad.xml-v1.0.dir/depend.internal".
Scanning dependencies of target autoquad.xml-v1.0
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
make -f CMakeFiles/autoquad.xml-v1.0.dir/build.make CMakeFiles/autoquad.xml-v1.0.dir/build
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[ 93%] Generating include/v1.0/autoquad/autoquad.h
/usr/bin/env PYTHONPATH="/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink:" /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=1.0 --output=include/v1.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/autoquad.xml
 * ACCESS DENIED:  mkdir:        /root/cache
WARNING: Unable to load XML validator libraries. XML validation will not be performed
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/autoquad.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/autoquad.xml
Note: message AQ_TELEMETRY_F is longer than 64 bytes long (90 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml
Ignoring MAVLink2 message SETUP_SIGNING
Ignoring MAVLink2 message BUTTON_CHANGE
Ignoring MAVLink2 message PLAY_TUNE
Ignoring MAVLink2 message CAMERA_INFORMATION
Ignoring MAVLink2 message CAMERA_SETTINGS
Ignoring MAVLink2 message STORAGE_INFORMATION
Ignoring MAVLink2 message CAMERA_CAPTURE_STATUS
Ignoring MAVLink2 message CAMERA_IMAGE_CAPTURED
Ignoring MAVLink2 message FLIGHT_INFORMATION
Ignoring MAVLink2 message MOUNT_ORIENTATION
Ignoring MAVLink2 message LOGGING_DATA
Ignoring MAVLink2 message LOGGING_DATA_ACKED
Ignoring MAVLink2 message LOGGING_ACK
Note: message GPS_STATUS is longer than 64 bytes long (109 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ATTITUDE_QUATERNION_COV is longer than 64 bytes long (80 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GLOBAL_POSITION_INT_COV is longer than 64 bytes long (189 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOCAL_POSITION_NED_COV is longer than 64 bytes long (233 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_ACTUATOR_CONTROLS is longer than 64 bytes long (89 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIGHRES_IMU is longer than 64 bytes long (70 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_SENSOR is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SIM_STATE is longer than 64 bytes long (92 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FILE_TRANSFER_PROTOCOL is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_STATE_QUATERNION is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOG_DATA is longer than 64 bytes long (105 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INJECT_DATA is longer than 64 bytes long (121 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_CONTROL is longer than 64 bytes long (87 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ENCAPSULATED_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message RESOURCE_REQUEST is longer than 64 bytes long (251 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FOLLOW_TARGET is longer than 64 bytes long (101 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CONTROL_SYSTEM_STATE is longer than 64 bytes long (108 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message AUTOPILOT_VERSION is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INPUT is longer than 64 bytes long (71 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_RTCM_DATA is longer than 64 bytes long (190 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message V2_EXTENSION is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Merged enum MAV_CMD
Merged enum MAV_DATA_STREAM
Note: An enum value was auto-generated: AQ_MAVLINK_DEFS_VERSION_1 = 1
Note: An enum value was auto-generated: MAV_DATA_STREAM_PROPULSION = 13
Found 138 MAVLink message types in 2 XML files
Generating C implementation in directory include/v1.0/autoquad
Generating C implementation in directory include/v1.0/common
Copying fixed headers for protocol 1.0 to include/v1.0
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[ 93%] Built target autoquad.xml-v1.0
make -f CMakeFiles/common.xml-v1.0.dir/build.make CMakeFiles/common.xml-v1.0.dir/depend
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
cd /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/common.xml-v1.0.dir/DependInfo.cmake
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/common.xml-v1.0.dir/DependInfo.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/common.xml-v1.0.dir/depend.internal".
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/common.xml-v1.0.dir/depend.internal".
Scanning dependencies of target common.xml-v1.0
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
make -f CMakeFiles/common.xml-v1.0.dir/build.make CMakeFiles/common.xml-v1.0.dir/build
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
make[2]: Nothing to be done for 'CMakeFiles/common.xml-v1.0.dir/build'.
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[ 96%] Built target common.xml-v1.0
make -f CMakeFiles/ualberta.xml-v1.0.dir/build.make CMakeFiles/ualberta.xml-v1.0.dir/depend
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
cd /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/ualberta.xml-v1.0.dir/DependInfo.cmake
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/ualberta.xml-v1.0.dir/DependInfo.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/ualberta.xml-v1.0.dir/depend.internal".
Dependee "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles/ualberta.xml-v1.0.dir/depend.internal".
Scanning dependencies of target ualberta.xml-v1.0
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
make -f CMakeFiles/ualberta.xml-v1.0.dir/build.make CMakeFiles/ualberta.xml-v1.0.dir/build
make[2]: Entering directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[100%] Generating include/v1.0/ualberta/ualberta.h
/usr/bin/env PYTHONPATH="/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink:" /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=1.0 --output=include/v1.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ualberta.xml
 * ACCESS DENIED:  mkdir:        /root/cache
WARNING: Unable to load XML validator libraries. XML validation will not be performed
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ualberta.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ualberta.xml
Validation skipped for /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml.
Parsing /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml
Ignoring MAVLink2 message SETUP_SIGNING
Ignoring MAVLink2 message BUTTON_CHANGE
Ignoring MAVLink2 message PLAY_TUNE
Ignoring MAVLink2 message CAMERA_INFORMATION
Ignoring MAVLink2 message CAMERA_SETTINGS
Ignoring MAVLink2 message STORAGE_INFORMATION
Ignoring MAVLink2 message CAMERA_CAPTURE_STATUS
Ignoring MAVLink2 message CAMERA_IMAGE_CAPTURED
Ignoring MAVLink2 message FLIGHT_INFORMATION
Ignoring MAVLink2 message MOUNT_ORIENTATION
Ignoring MAVLink2 message LOGGING_DATA
Ignoring MAVLink2 message LOGGING_DATA_ACKED
Ignoring MAVLink2 message LOGGING_ACK
Note: message GPS_STATUS is longer than 64 bytes long (109 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ATTITUDE_QUATERNION_COV is longer than 64 bytes long (80 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GLOBAL_POSITION_INT_COV is longer than 64 bytes long (189 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOCAL_POSITION_NED_COV is longer than 64 bytes long (233 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_ACTUATOR_CONTROLS is longer than 64 bytes long (89 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIGHRES_IMU is longer than 64 bytes long (70 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_SENSOR is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SIM_STATE is longer than 64 bytes long (92 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FILE_TRANSFER_PROTOCOL is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_STATE_QUATERNION is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOG_DATA is longer than 64 bytes long (105 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INJECT_DATA is longer than 64 bytes long (121 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_CONTROL is longer than 64 bytes long (87 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ENCAPSULATED_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message RESOURCE_REQUEST is longer than 64 bytes long (251 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FOLLOW_TARGET is longer than 64 bytes long (101 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CONTROL_SYSTEM_STATE is longer than 64 bytes long (108 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message AUTOPILOT_VERSION is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INPUT is longer than 64 bytes long (71 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_RTCM_DATA is longer than 64 bytes long (190 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message V2_EXTENSION is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: An enum value was auto-generated: MODE_MANUAL_DIRECT = 1
Note: An enum value was auto-generated: MODE_MANUAL_SCALED = 2
Note: An enum value was auto-generated: MODE_AUTO_PID_ATT = 3
Note: An enum value was auto-generated: MODE_AUTO_PID_VEL = 4
Note: An enum value was auto-generated: MODE_AUTO_PID_POS = 5
Note: An enum value was auto-generated: NAV_AHRS_INIT = 1
Note: An enum value was auto-generated: NAV_AHRS = 2
Note: An enum value was auto-generated: NAV_INS_GPS_INIT = 3
Note: An enum value was auto-generated: NAV_INS_GPS = 4
Note: An enum value was auto-generated: PILOT_MANUAL = 1
Note: An enum value was auto-generated: PILOT_AUTO = 2
Note: An enum value was auto-generated: PILOT_ROTO = 3
Found 139 MAVLink message types in 2 XML files
Generating C implementation in directory include/v1.0/ualberta
Generating C implementation in directory include/v1.0/common
Copying fixed headers for protocol 1.0 to include/v1.0
make[2]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
[100%] Built target ualberta.xml-v1.0
make[1]: Leaving directory '/var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7'
/usr/bin/cmake -E cmake_progress_start /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink-python2_7/CMakeFiles 0
>>> Source compiled.
 * --------------------------- ACCESS VIOLATION SUMMARY ---------------------------
 * LOG FILE: "/var/log/sandbox/sandbox-8459.log"
 * 
VERSION 1.0
FORMAT: F - Function called
FORMAT: S - Access Status
FORMAT: P - Path as passed to function
FORMAT: A - Absolute Path (not canonical)
FORMAT: R - Canonical Path
FORMAT: C - Command Line

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=1.0 --output=include/v1.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ardupilotmega.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=1.0 --output=include/v1.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/standard.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/uAvionix.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C++11 --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/uAvionix.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=1.0 --output=include/v1.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/matrixpilot.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/standard.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C++11 --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/standard.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/slugs.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C++11 --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/slugs.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ardupilotmega.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C++11 --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ardupilotmega.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ASLUAV.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C++11 --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ASLUAV.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/paparazzi.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C++11 --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/paparazzi.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/autoquad.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C++11 --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/autoquad.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/matrixpilot.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C++11 --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/matrixpilot.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/port * 
age/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ualberta.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C++11 --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ualberta.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C++11 --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/common.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=1.0 --output=include/v1.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/paparazzi.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=1.0 --output=include/v1.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/slugs.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=1.0 --output=include/v1.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ASLUAV.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=1.0 --output=include/v1.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/autoquad.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=1.0 --output=include/v1.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ualberta.xml 
ev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C++11 --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/slugs.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ardupilotmega.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C++11 --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ardupilotmega.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ASLUAV.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C++11 --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/ASLUAV.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/paparazzi.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C++11 --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/paparazzi.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/autoquad.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C++11 --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/autoquad.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/matrixpilot.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/pymavlink/tools/mavgen.py --lang=C++11 --wire-protocol=2.0 --output=include/v2.0 /var/tmp/portage/dev-ros/mavlink-gbp-release-2017.2.7-r1/work/mavlink-gbp-release-release-kinetic-mavlink/message_definitions/v1.0/matrixpilot.xml 

F: mkdir
S: deny
P: /root/cache
A: /root/cache
R: /root/cache
C: /usr/bin/python2.7 /var/tmp/port * --------------------------------------------------------------------------------