Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
ArduPilot waf build failure inside of vagrant vm
Dmitriys-MBP:ardupilot dipspb$ vagrant up
.
.
.
Dmitriys-MBP:ardupilot dipspb$ vagrant rsync
Dmitriys-MBP:ardupilot dipspb$ vagrant ssh
Welcome to Ubuntu 16.10 (GNU/Linux 4.8.0-26-generic i686)
* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/advantage
Get cloud support with Ubuntu Advantage Cloud Guest:
http://www.ubuntu.com/business/services/cloud
25 packages can be updated.
15 updates are security updates.
Last login: Wed Dec 7 12:41:30 2016 from 10.0.2.2
Ardupilot environment ready. Run 'sim_vehicle.py' to start simulating an arducopter instance.
or run 'make sitl' to just do a test build.
ubuntu@ubuntu-yakkety:/vagrant/ArduCopter$ cd ..
ubuntu@ubuntu-yakkety:/vagrant$ rm -rf modules/* ; git submodule sync ; git submodule update --init --recursive
Synchronizing submodule url for 'modules/PX4Firmware'
Synchronizing submodule url for 'modules/PX4NuttX'
Synchronizing submodule url for 'modules/gbenchmark'
Synchronizing submodule url for 'modules/gtest'
Synchronizing submodule url for 'modules/mavlink'
Synchronizing submodule url for 'modules/uavcan'
Synchronizing submodule url for 'modules/waf'
Submodule path 'modules/PX4Firmware': checked out '725bcec259aeb43b229114382916529d017ec14b'
Submodule path 'modules/PX4Firmware/Tools/gencpp': checked out '26a86f04bcec0018af6652b3ddd3f680e6e3fa2a'
Submodule path 'modules/PX4Firmware/Tools/genmsg': checked out '72f0383f0e6a489214c51802ae12d6e271b1e454'
Submodule path 'modules/PX4Firmware/mavlink/include/mavlink/v1.0': checked out 'bf251caef3dbf610e5152115a2d81e00e54ab7e7'
Submodule path 'modules/PX4Firmware/src/lib/DriverFramework': checked out 'd6ef668f4564e1c158910c52df7d71114bd2ca4e'
Submodule path 'modules/PX4Firmware/src/lib/DriverFramework/cmake/cmake_hexagon': checked out 'ba681fcd0d4c5ac95636dd8e9d8536dbd81beabd'
Submodule path 'modules/PX4Firmware/src/lib/DriverFramework/dspal': checked out '8f39699c6b79447f32f0714629da790bbf271aa5'
Submodule path 'modules/PX4Firmware/src/lib/DriverFramework/dspal/test/dspal_tester/cmake_hexagon': checked out 'ba681fcd0d4c5ac95636dd8e9d8536dbd81beabd'
Submodule path 'modules/PX4Firmware/src/lib/ecl': checked out 'f86ef3478219b4b1c31e17b8f308df4b69eda2f7'
Submodule path 'modules/PX4Firmware/src/lib/ecl/matrix': checked out '95e3d7d6ce5274d9b7fec76c0093dc5eaa381abf'
Submodule path 'modules/PX4Firmware/src/lib/matrix': checked out '07fba8322a16cb2dac47e6a8ac7d21ec346313ff'
Submodule path 'modules/PX4Firmware/src/modules/uavcan/libuavcan': checked out '702f6f05608885d3be993edb01394212bd2dade1'
Submodule path 'modules/PX4Firmware/src/modules/uavcan/libuavcan/dsdl': checked out '9804a3e6972825586be252ce08dd899f44994b14'
Submodule path 'modules/PX4Firmware/src/modules/uavcan/libuavcan/libuavcan/dsdl_compiler/pyuavcan': checked out 'c58477a644d20ccf95a20c151f3a0402f271c3b8'
Submodule path 'modules/PX4Firmware/src/modules/uavcan/libuavcan/libuavcan/dsdl_compiler/pyuavcan/dsdl': checked out 'fd12483ddd4e58242d61d74a163e7aeaa1e0f466'
Submodule path 'modules/PX4NuttX': checked out '8c9659921c0d42a0e909a5ecdba93e9d9a4b0a7e'
Submodule path 'modules/gbenchmark': checked out '006d23ccca1375a973b7fae0cc351cedb41b812a'
Submodule path 'modules/gtest': checked out 'c99458533a9b4c743ed51537e25989ea55944908'
Submodule path 'modules/mavlink': checked out '606e970c41e4c0da1ca2ec323a31b89e9e290f7a'
Submodule path 'modules/mavlink/pymavlink': checked out '38f866bbda700ef9dd652b52c7917a81a7dc7750'
Submodule path 'modules/uavcan': checked out '71cf39c8c6c3c2709bc1a32ffd947add22b1a836'
Submodule path 'modules/uavcan/dsdl': checked out '9804a3e6972825586be252ce08dd899f44994b14'
Submodule path 'modules/uavcan/libuavcan/dsdl_compiler/pyuavcan': checked out 'c58477a644d20ccf95a20c151f3a0402f271c3b8'
Submodule path 'modules/uavcan/libuavcan/dsdl_compiler/pyuavcan/dsdl': checked out 'fd12483ddd4e58242d61d74a163e7aeaa1e0f466'
Submodule path 'modules/waf': checked out '73163ef5c117a51f29546d17c2bb2041aecefcdd'
ubuntu@ubuntu-yakkety:/vagrant$ ./waf configure --board px4-v2 ; ./waf --target bin/arducopter-quad
Setting top to : /vagrant
Setting out to : /vagrant/build
Autoconfiguration : enabled
Setting board to : px4-v2
Checking for program 'arm-none-eabi-ar' : /opt/gcc-arm-none-eabi-4_9-2015q3/bin/arm-none-eabi-ar
Using toolchain : arm-none-eabi
Checking for 'g++' (C++ compiler) : /opt/gcc-arm-none-eabi-4_9-2015q3/bin/arm-none-eabi-g++
Checking for 'gcc' (C compiler) : /opt/gcc-arm-none-eabi-4_9-2015q3/bin/arm-none-eabi-gcc
Checking for HAVE_CMATH_ISFINITE : no
Checking for HAVE_CMATH_ISINF : no
Checking for HAVE_CMATH_ISNAN : no
Checking for NEED_CMATH_ISFINITE_STD_NAMESPACE : no
Checking for NEED_CMATH_ISINF_STD_NAMESPACE : no
Checking for NEED_CMATH_ISNAN_STD_NAMESPACE : no
Checking for header endian.h : not found
Checking for header byteswap.h : not found
Checking for program 'cmake' : /usr/bin/cmake
Checking cmake version : 3.5.2
Checking for program 'ninja, ninja-build' : not found
Checking for program 'make' : /usr/bin/make
Checking for program 'python' : /usr/bin/python
Checking for python version >= 2.7.0 : 2.7.12
Source is git repository : yes
Update submodules : yes
Checking for program 'git' : /usr/bin/git
Gtest : PX4 boards currently don't support compiling gtest
Checking for program 'arm-none-eabi-size' : /opt/gcc-arm-none-eabi-4_9-2015q3/bin/arm-none-eabi-size
Benchmarks : disabled
Unit tests : disabled
'configure' finished successfully (1.337s)
Waf: Entering directory `/vagrant/build/px4-v2'
[ 5/14] Processing modules/mavlink/message_definitions/v1.0/ardupilotmega.xml
Validating /vagrant/modules/mavlink/message_definitions/v1.0/ardupilotmega.xml
Parsing /vagrant/modules/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.
Validating /vagrant/modules/mavlink/message_definitions/v1.0/common.xml
Parsing /vagrant/modules/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 (76 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 (193 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 (237 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.
Validating /vagrant/modules/mavlink/message_definitions/v1.0/uAvionix.xml
Parsing /vagrant/modules/mavlink/message_definitions/v1.0/uAvionix.xml
Merged enum MAV_CMD
Found 195 MAVLink message types in 3 XML files
Generating C implementation in directory /vagrant/build/px4-v2/libraries/GCS_MAVLink/include/mavlink/v2.0/ardupilotmega
Generating C implementation in directory /vagrant/build/px4-v2/libraries/GCS_MAVLink/include/mavlink/v2.0/common
Generating C implementation in directory /vagrant/build/px4-v2/libraries/GCS_MAVLink/include/mavlink/v2.0/uAvionix
Copying fixed headers for protocol 2.0 to /vagrant/build/px4-v2/libraries/GCS_MAVLink/include/mavlink/v2.0
[13/14] CMake Build px4 msg_gen
-- nuttx-px4fmu-v2-apm
-- could not find gdbtui
-- could not find ddd
-- CMAKE_BUILD_TYPE : RelWithDebInfo : Build type.
-- CMAKE_CXX_FLAGS : -g -fno-exceptions -fno-rtti -std=gnu++0x -fno-threadsafe-statics -DCONFIG_WCHAR_BUILTIN -D__CUSTOM_FILE_IO__ -Wall -Werror -Wextra -Wno-sign-compare -Wfloat-equal -Wpointer-arith -Wmissing-declarations -Wno-unused-parameter -Werror=format-security -Werror=array-bounds -Wfatal-errors -Werror=unused-variable -Werror=reorder -Werror=uninitialized -Werror=init-self -Wframe-larger-than=1024 -Werror=unused-but-set-variable -Wformat=1 -Wdouble-promotion -Werror=double-promotion -Wno-missing-field-initializers -Os -fno-strict-aliasing -fomit-frame-pointer -funsafe-math-optimizations -ffunction-sections -fdata-sections -fno-strength-reduce -fno-builtin-printf -fvisibility=hidden -include visibility.h -mcpu=cortex-m4 -mthumb -march=armv7e-m -mfpu=fpv4-sp-d16 -mfloat-abi=hard -nodefaultlibs -nostdlib -Wno-error=double-promotion -Wno-error=reorder -DCMAKE_BUILD -DARDUPILOT_BUILD -I/vagrant/build/px4-v2/libraries/GCS_MAVLink -I/vagrant/build/px4-v2/libraries/GCS_MAVLink/include/mavlink -Wl,--gc-sections : C++ flags.
-- CMAKE_C_FLAGS : -g -std=gnu99 -fno-common -Wall -Werror -Wextra -Wno-sign-compare -Wfloat-equal -Wpointer-arith -Wmissing-declarations -Wno-unused-parameter -Werror=format-security -Werror=array-bounds -Wfatal-errors -Werror=unused-variable -Werror=reorder -Werror=uninitialized -Werror=init-self -Wframe-larger-than=1024 -Werror=unused-but-set-variable -Wformat=1 -Wdouble-promotion -Werror=double-promotion -Wbad-function-cast -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wold-style-declaration -Wmissing-parameter-type -Os -fno-strict-aliasing -fomit-frame-pointer -funsafe-math-optimizations -ffunction-sections -fdata-sections -fno-strength-reduce -fno-builtin-printf -fvisibility=hidden -include visibility.h -mcpu=cortex-m4 -mthumb -march=armv7e-m -mfpu=fpv4-sp-d16 -mfloat-abi=hard -nodefaultlibs -nostdlib -DCMAKE_BUILD : C flags.
-- UAVCAN_USE_CPP03 : ON : Use C++03 standard.
-- UAVCAN_PLATFORM : stm32 : Platform.
-- CONTINUOUS_INTEGRATION_BUILD : OFF : Disable error redirection and timing tests
-- Debug build: 0
running build
running build_py
creating build
creating build/lib.linux-i686-2.7
creating build/lib.linux-i686-2.7/libuavcan_dsdl_compiler
copying libuavcan_dsdl_compiler/__init__.py -> build/lib.linux-i686-2.7/libuavcan_dsdl_compiler
copying libuavcan_dsdl_compiler/pyratemp.py -> build/lib.linux-i686-2.7/libuavcan_dsdl_compiler
copying libuavcan_dsdl_compiler/data_type_template.tmpl -> build/lib.linux-i686-2.7/libuavcan_dsdl_compiler
running build_scripts
creating build/scripts-2.7
copying and adjusting libuavcan_dsdlc -> build/scripts-2.7
changing mode of build/scripts-2.7/libuavcan_dsdlc from 644 to 755
-- Using C++03
-- Release build type: RelWithDebInfo
-- Adding STM32 platform driver
-- GIT_DESC = 725bcec259aeb43b229114382916529d017ec14b
-- Configuring done
-- Generating done
-- Build files have been written to: /vagrant/build/px4-v2/modules/PX4Firmware
[ 50%] Generating git_init_Tools_genmsg.stamp
[ 50%] Built target git_genmsg
[ 50%] Generating git_init_Tools_gencpp.stamp
[ 50%] Built target git_gencpp
[ 50%] Generating uORB topic multi headers for nuttx
[100%] Generating uORB topic headers
[100%] Built target msg_gen
INCLUDE_DIRS=/vagrant/modules/PX4Firmware/src;/vagrant/build/px4-v2/modules/PX4Firmware;/vagrant/build/px4-v2/modules/PX4Firmware/src;/vagrant/modules/PX4Firmware/src/modules;/vagrant/modules/PX4Firmware/src/include;/vagrant/modules/PX4Firmware/src/lib;/vagrant/modules/PX4Firmware/src/platforms;/vagrant/modules/PX4Firmware/src/drivers/boards/px4fmu-v2;/vagrant/build/px4-v2/modules/PX4Firmware;/vagrant/build/px4-v2/modules/PX4Firmware/src/modules/px4_messages;/vagrant/build/px4-v2/modules/PX4Firmware/src/modules;/vagrant/modules/PX4Firmware/mavlink/include/mavlink;/vagrant/modules/PX4Firmware/src/lib/DriverFramework/framework/include;src/lib/matrix;/vagrant/build/px4-v2/modules/PX4Firmware/px4fmu-v2/NuttX/nuttx-export/include;/vagrant/build/px4-v2/modules/PX4Firmware/px4fmu-v2/NuttX/nuttx-export/include/cxx;/vagrant/build/px4-v2/modules/PX4Firmware/px4fmu-v2/NuttX/nuttx-export/arch/chip;/vagrant/build/px4-v2/modules/PX4Firmware/px4fmu-v2/NuttX/nuttx-export/arch/common
ADDING DRIVERS
[14/14] CMake Build px4 prebuild_targets
Built target __nuttx_patch_px4fmu-v2
Built target __nuttx_copy_px4fmu-v2
Generating px4fmu-v2.export
Configuring NuttX for px4fmu-v2
Makefile.unix:438: recipe for target 'clean_context' failed
CMakeFiles/nuttx_export_px4fmu-v2.dir/build.make:74: recipe for target 'px4fmu-v2.export' failed
CMakeFiles/Makefile2:196: recipe for target 'CMakeFiles/nuttx_export_px4fmu-v2.dir/all' failed
CMakeFiles/Makefile2:811: recipe for target 'CMakeFiles/prebuild_targets.dir/rule' failed
Makefile:494: recipe for target 'prebuild_targets' failed
make[4]: /vagrant/build/px4-v2/modules/PX4Firmware/px4fmu-v2/NuttX/nuttx/tools/unlink.sh: Command not found
make[4]: *** [clean_context] Error 127
make[3]: *** [px4fmu-v2.export] Error 2
make[2]: *** [CMakeFiles/nuttx_export_px4fmu-v2.dir/all] Error 2
make[1]: *** [CMakeFiles/prebuild_targets.dir/rule] Error 2
make: *** [prebuild_targets] Error 2
Waf: Leaving directory `/vagrant/build/px4-v2'
Build failed
-> task in 'px4_prebuild_targets' failed (exit status 2):
{task 3068277980L: cmake_build_task -> }
['/usr/bin/cmake', '--build', '/vagrant/build/px4-v2/modules/PX4Firmware', '--target', 'prebuild_targets']
ubuntu@ubuntu-yakkety:/vagrant$
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.