Servers by jDrones

Cygwin64 build fails on Windows10

I have strictly followed the every step of Docs on ‘Downloading the code/using Git’ and ‘Building the code – Setting up the waf Build Environment on Windows using Cygwin’. I have updated git submodules and installed all the software and packages required. I have been trying for 3 days. The configure build succeed. However, ./waf copter keeps to be failed. I don’t know where the problem is. Also, there are huge number of notes about message lengths mismatch. Below is the build information of the Cygwin64 Terminal. Could someone help me fix this out? Thanks a lot.

$ ./waf configure --board fmuv3
Setting top to : /cygdrive/c/ardupilot
Setting out to : /cygdrive/c/ardupilot/build
Autoconfiguration : enabled
Setting board to : fmuv3
Using toolchain : arm-none-eabi
Checking for ‘g++’ (C++ compiler) : /cygdrive/c/Program Files (x86)/GNU Tools ARM Embedded/6 2017-q2-update/bin/arm-none-eabi-g++
Checking for ‘gcc’ (C compiler) : /cygdrive/c/Program Files (x86)/GNU Tools ARM Embedded/6 2017-q2-update/bin/arm-none-eabi-gcc
Checking for c flags ‘-MMD’ : yes
Checking for cxx flags ‘-MMD’ : yes
Checking for program ‘make’ : /usr/bin/make
Checking for program ‘arm-none-eabi-objcopy’ : /cygdrive/c/Program Files (x86)/GNU Tools ARM Embedded/6 2017-q2-update/bin/arm-none-eabi-objcopy
Setup for MCU STM32F427xx
Writing hwdef setup in /cygdrive/c/ardupilot/build/fmuv3/hwdef.h
Writing DMA map
Generating ldscript.ld
No default parameter file found
Checking for env.py
env set HAL_WITH_UAVCAN=1
env set PROCESS_STACK=0x2000
env set MAIN_STACK=0x400
env set IOMCU_FW=0
env set PERIPH_FW=0
env set BOARD_FLASH_SIZE=2048
env set CPU_FLAGS=[’-mcpu=cortex-m4’, ‘-mfpu=fpv4-sp-d16’, ‘-mfloat-abi=hard’, ‘-DARM_MATH_CM4’, ‘-u_printf_float’]
env set CORTEX=cortex-m4
env set APJ_BOARD_ID=9
env set APJ_BOARD_TYPE=STM32F427xx
env set USBID=0x1209/0x5741
env set FLASH_RESERVE_START_KB=16
env set CHIBIOS_BUILD_FLAGS=USE_FATFS=yes CHIBIOS_STARTUP_MK=os/common/startup/ARMCMx/compilers/GCC/mk/startup_stm32f4xx.mk CHIBIOS_PLATFORM_MK=os/hal/ports/STM32/STM32F4xx/platform.mk MCU=cortex-m4 ENV_UDEFS=-DCHPRINTF_USE_FLOAT=1
Enabling ChibiOS asserts : no
Checking for intelhex module: : disabled
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 HAVE_MEMRCHR : no
Checking for program ‘python’ : /usr/bin/python
Checking for python version >= 2.7.0 : 3.6.9
Checking for program ‘python’ : /usr/bin/python
Checking for python version >= 2.7.0 : 3.6.9
Source is git repository : yes
Update submodules : yes
Checking for program ‘git’ : /usr/bin/git
Gtest : STM32 boards currently don’t support compiling gtest
Checking for program ‘arm-none-eabi-size’ : /cygdrive/c/Program Files (x86)/GNU Tools ARM Embedded/6 2017-q2-update/bin/arm-none-eabi-size
Benchmarks : disabled
Unit tests : disabled
Scripting : enabled
Scripting runtime checks : enabled
Checking for program ‘rsync’ : /usr/bin/rsync
‘configure’ finished successfully (2.526s)

$ ./waf copter
Waf: Entering directory `/cygdrive/c/ardupilot/build/fmuv3’
Checking for env.py
env added HAL_WITH_UAVCAN=1
env added PROCESS_STACK=0x2000
env added MAIN_STACK=0x400
env added IOMCU_FW=0
env added PERIPH_FW=0
env added BOARD_FLASH_SIZE=2048
env appended CPU_FLAGS=[’-mcpu=cortex-m4’, ‘-mfpu=fpv4-sp-d16’, ‘-mfloat-abi=hard’, ‘-DARM_MATH_CM4’, ‘-u_printf_float’]
env added CORTEX=cortex-m4
env added APJ_BOARD_ID=9
env added APJ_BOARD_TYPE=STM32F427xx
env added USBID=0x1209/0x5741
env added FLASH_RESERVE_START_KB=16
env added CHIBIOS_BUILD_FLAGS=USE_FATFS=yes CHIBIOS_STARTUP_MK=os/common/startup/ARMCMx/compilers/GCC/mk/startup_stm32f4xx.mk CHIBIOS_PLATFORM_MK=os/hal/ports/STM32/STM32F4xx/platform.mk MCU=cortex-m4 ENV_UDEFS=-DCHPRINTF_USE_FLOAT=1
Embedding file bootloader.bin:/cygdrive/c/ardupilot/Tools/bootloaders/fmuv3_bl.bin
Embedding file hwdef.dat:/cygdrive/c/ardupilot/build/fmuv3/hw.dat
Embedding file io_firmware.bin:Tools/IO_Firmware/iofirmware_lowpolh.bin
[ 3/10] Creating build/fmuv3/hwdef.h
[ 4/10] Creating build/fmuv3/modules/ChibiOS/include_dirs
[ 5/10] Compiling libraries/AP_Scripting/generator/src/main.c
[ 6/10] Processing modules/mavlink/message_definitions/v1.0/ardupilotmega.xml
[ 7/10] Processing uavcangen: libraries/AP_UAVCAN/dsdl/ardupilot libraries/AP_UAVCAN/dsdl/com modules/uavcan/dsdl/uavcan
[ 8/10] Creating build/fmuv3/ap_version.h
Validation skipped for /cygdrive/c/ardupilot/modules/mavlink/message_definitions/v1.0/ardupilotmega.xml.
Parsing /cygdrive/c/ardupilot/modules/mavlink/message_definitions/v1.0/ardupilotmega.xml
MAV_CMD
MAV_CMD_DO_GRIPPER
MAV_CMD_DO_AUTOTUNE_ENABLE
MAV_CMD_DO_SET_RESUME_REPEAT_DIST
MAV_CMD_NAV_ALTITUDE_WAIT
MAV_CMD_POWER_OFF_INITIATED
MAV_CMD_SOLO_BTN_FLY_CLICK
MAV_CMD_SOLO_BTN_FLY_HOLD
MAV_CMD_SOLO_BTN_PAUSE_CLICK
MAV_CMD_FIXED_MAG_CAL
MAV_CMD_FIXED_MAG_CAL_FIELD
MAV_CMD_FIXED_MAG_CAL_YAW
MAV_CMD_DO_START_MAG_CAL
MAV_CMD_DO_ACCEPT_MAG_CAL
MAV_CMD_DO_CANCEL_MAG_CAL
MAV_CMD_ACCELCAL_VEHICLE_POS
MAV_CMD_DO_SEND_BANNER
MAV_CMD_SET_FACTORY_TEST_MODE
MAV_CMD_GIMBAL_RESET
MAV_CMD_GIMBAL_AXIS_CALIBRATION_STATUS
MAV_CMD_GIMBAL_REQUEST_AXIS_CALIBRATION
MAV_CMD_GIMBAL_FULL_RESET
MAV_CMD_DO_WINCH
MAV_CMD_FLASH_BOOTLOADER
MAV_CMD_BATTERY_RESET
MAV_CMD_DEBUG_TRAP
MAV_CMD_SCRIPTING
MAV_CMD_GUIDED_CHANGE_SPEED
MAV_CMD_GUIDED_CHANGE_ALTITUDE
MAV_CMD_GUIDED_CHANGE_HEADING
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 EFI_STATUS is longer than 64 bytes long (73 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 /cygdrive/c/ardupilot/modules/mavlink/message_definitions/v1.0/common.xml.
Parsing /cygdrive/c/ardupilot/modules/mavlink/message_definitions/v1.0/common.xml
MAV_CMD
MAV_CMD_NAV_WAYPOINT
MAV_CMD_NAV_LOITER_UNLIM
MAV_CMD_NAV_LOITER_TURNS
MAV_CMD_NAV_LOITER_TIME
MAV_CMD_NAV_RETURN_TO_LAUNCH
MAV_CMD_NAV_LAND
MAV_CMD_NAV_TAKEOFF
MAV_CMD_NAV_LAND_LOCAL
MAV_CMD_NAV_TAKEOFF_LOCAL
MAV_CMD_NAV_FOLLOW
MAV_CMD_NAV_CONTINUE_AND_CHANGE_ALT
MAV_CMD_NAV_LOITER_TO_ALT
MAV_CMD_DO_FOLLOW
MAV_CMD_DO_FOLLOW_REPOSITION
MAV_CMD_NAV_ROI
MAV_CMD_NAV_PATHPLANNING
MAV_CMD_NAV_SPLINE_WAYPOINT
MAV_CMD_NAV_VTOL_TAKEOFF
MAV_CMD_NAV_VTOL_LAND
MAV_CMD_NAV_GUIDED_ENABLE
MAV_CMD_NAV_DELAY
MAV_CMD_NAV_PAYLOAD_PLACE
MAV_CMD_NAV_LAST
MAV_CMD_CONDITION_DELAY
MAV_CMD_CONDITION_CHANGE_ALT
MAV_CMD_CONDITION_DISTANCE
MAV_CMD_CONDITION_YAW
MAV_CMD_CONDITION_LAST
MAV_CMD_DO_SET_MODE
MAV_CMD_DO_JUMP
MAV_CMD_DO_CHANGE_SPEED
MAV_CMD_DO_SET_HOME
MAV_CMD_DO_SET_PARAMETER
MAV_CMD_DO_SET_RELAY
MAV_CMD_DO_REPEAT_RELAY
MAV_CMD_DO_SET_SERVO
MAV_CMD_DO_REPEAT_SERVO
MAV_CMD_DO_FLIGHTTERMINATION
MAV_CMD_DO_CHANGE_ALTITUDE
MAV_CMD_DO_LAND_START
MAV_CMD_DO_RALLY_LAND
MAV_CMD_DO_GO_AROUND
MAV_CMD_DO_REPOSITION
MAV_CMD_DO_PAUSE_CONTINUE
MAV_CMD_DO_SET_REVERSE
MAV_CMD_DO_SET_ROI_LOCATION
MAV_CMD_DO_SET_ROI_WPNEXT_OFFSET
MAV_CMD_DO_SET_ROI_NONE
MAV_CMD_DO_SET_ROI_SYSID
MAV_CMD_DO_CONTROL_VIDEO
MAV_CMD_DO_SET_ROI
MAV_CMD_DO_DIGICAM_CONFIGURE
MAV_CMD_DO_DIGICAM_CONTROL
MAV_CMD_DO_MOUNT_CONFIGURE
MAV_CMD_DO_MOUNT_CONTROL
MAV_CMD_DO_SET_CAM_TRIGG_DIST
MAV_CMD_DO_FENCE_ENABLE
MAV_CMD_DO_PARACHUTE
MAV_CMD_DO_MOTOR_TEST
MAV_CMD_DO_INVERTED_FLIGHT
MAV_CMD_NAV_SET_YAW_SPEED
MAV_CMD_DO_SET_CAM_TRIGG_INTERVAL
MAV_CMD_DO_MOUNT_CONTROL_QUAT
MAV_CMD_DO_GUIDED_MASTER
MAV_CMD_DO_GUIDED_LIMITS
MAV_CMD_DO_ENGINE_CONTROL
MAV_CMD_DO_SET_MISSION_CURRENT
MAV_CMD_DO_LAST
MAV_CMD_PREFLIGHT_CALIBRATION
MAV_CMD_PREFLIGHT_SET_SENSOR_OFFSETS
MAV_CMD_PREFLIGHT_UAVCAN
MAV_CMD_PREFLIGHT_STORAGE
MAV_CMD_PREFLIGHT_REBOOT_SHUTDOWN
MAV_CMD_OVERRIDE_GOTO
MAV_CMD_MISSION_START
MAV_CMD_COMPONENT_ARM_DISARM
MAV_CMD_GET_HOME_POSITION
MAV_CMD_START_RX_PAIR
MAV_CMD_GET_MESSAGE_INTERVAL
MAV_CMD_SET_MESSAGE_INTERVAL
MAV_CMD_REQUEST_MESSAGE
MAV_CMD_REQUEST_AUTOPILOT_CAPABILITIES
MAV_CMD_REQUEST_CAMERA_INFORMATION
MAV_CMD_REQUEST_CAMERA_SETTINGS
MAV_CMD_REQUEST_STORAGE_INFORMATION
MAV_CMD_STORAGE_FORMAT
MAV_CMD_REQUEST_CAMERA_CAPTURE_STATUS
MAV_CMD_REQUEST_FLIGHT_INFORMATION
MAV_CMD_RESET_CAMERA_SETTINGS
MAV_CMD_SET_CAMERA_MODE
MAV_CMD_JUMP_TAG
MAV_CMD_DO_JUMP_TAG
MAV_CMD_IMAGE_START_CAPTURE
MAV_CMD_IMAGE_STOP_CAPTURE
MAV_CMD_DO_TRIGGER_CONTROL
MAV_CMD_VIDEO_START_CAPTURE
MAV_CMD_VIDEO_STOP_CAPTURE
MAV_CMD_LOGGING_START
MAV_CMD_LOGGING_STOP
MAV_CMD_AIRFRAME_CONFIGURATION
MAV_CMD_CONTROL_HIGH_LATENCY
MAV_CMD_PANORAMA_CREATE
MAV_CMD_DO_VTOL_TRANSITION
MAV_CMD_ARM_AUTHORIZATION_REQUEST
MAV_CMD_SET_GUIDED_SUBMODE_STANDARD
MAV_CMD_SET_GUIDED_SUBMODE_CIRCLE
MAV_CMD_NAV_FENCE_RETURN_POINT
MAV_CMD_NAV_FENCE_POLYGON_VERTEX_INCLUSION
MAV_CMD_NAV_FENCE_POLYGON_VERTEX_EXCLUSION
MAV_CMD_NAV_FENCE_CIRCLE_INCLUSION
MAV_CMD_NAV_FENCE_CIRCLE_EXCLUSION
MAV_CMD_NAV_RALLY_POINT
MAV_CMD_UAVCAN_GET_NODE_INFO
MAV_CMD_PAYLOAD_PREPARE_DEPLOY
MAV_CMD_PAYLOAD_CONTROL_DEPLOY
MAV_CMD_WAYPOINT_USER_1
MAV_CMD_WAYPOINT_USER_2
MAV_CMD_WAYPOINT_USER_3
MAV_CMD_WAYPOINT_USER_4
MAV_CMD_WAYPOINT_USER_5
MAV_CMD_SPATIAL_USER_1
MAV_CMD_SPATIAL_USER_2
MAV_CMD_SPATIAL_USER_3
MAV_CMD_SPATIAL_USER_4
MAV_CMD_SPATIAL_USER_5
MAV_CMD_USER_1
MAV_CMD_USER_2
MAV_CMD_USER_3
MAV_CMD_USER_4
MAV_CMD_USER_5
MAV_CMD_ACK
MAV_CMD_ACK_OK
MAV_CMD_ACK_ERR_FAIL
MAV_CMD_ACK_ERR_ACCESS_DENIED
MAV_CMD_ACK_ERR_NOT_SUPPORTED
MAV_CMD_ACK_ERR_COORDINATE_FRAME_NOT_SUPPORTED
MAV_CMD_ACK_ERR_COORDINATES_OUT_OF_RANGE
MAV_CMD_ACK_ERR_X_LAT_OUT_OF_RANGE
MAV_CMD_ACK_ERR_Y_LON_OUT_OF_RANGE
MAV_CMD_ACK_ERR_Z_ALT_OUT_OF_RANGE
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 GLOBAL_VISION_POSITION_ESTIMATE is longer than 64 bytes long (125 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message VISION_POSITION_ESTIMATE is longer than 64 bytes long (125 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message VISION_SPEED_ESTIMATE is longer than 64 bytes long (65 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message VICON_POSITION_ESTIMATE is longer than 64 bytes long (124 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 (71 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 ATT_POS_MOCAP is longer than 64 bytes long (128 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 (86 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LANDING_TARGET 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 (73 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 HOME_POSITION 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 SET_HOME_POSITION 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 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 PLAY_TUNE is longer than 64 bytes long (240 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Setup for MCU STM32F427xx
Writing hwdef setup in /cygdrive/c/ardupilot/build/fmuv3/hwdef.h
Writing DMA map
Generating ldscript.ld
No default parameter file found
Note: message CAMERA_INFORMATION is longer than 64 bytes long (243 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: message WIFI_CONFIG_AP is longer than 64 bytes long (104 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message AIS_VESSEL 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 UAVCAN_NODE_INFO is longer than 64 bytes long (124 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message OBSTACLE_DISTANCE is longer than 64 bytes long (175 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ODOMETRY is longer than 64 bytes long (240 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message DEBUG_FLOAT_ARRAY is longer than 64 bytes long (260 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message STATUSTEXT_LONG 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 ACTUATOR_OUTPUT_STATUS is longer than 64 bytes long (148 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message WHEEL_DISTANCE is longer than 64 bytes long (145 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Validation skipped for /cygdrive/c/ardupilot/modules/mavlink/message_definitions/v1.0/uAvionix.xml.
Parsing /cygdrive/c/ardupilot/modules/mavlink/message_definitions/v1.0/uAvionix.xml
Validation skipped for /cygdrive/c/ardupilot/modules/mavlink/message_definitions/v1.0/icarous.xml.
Parsing /cygdrive/c/ardupilot/modules/mavlink/message_definitions/v1.0/icarous.xml
Merged enum MAV_CMD
Found 226 MAVLink message types in 4 XML files
Generating C implementation in directory /cygdrive/c/ardupilot/build/fmuv3/libraries/GCS_MAVLink/include/mavlink/v2.0/ardupilotmega
Generating C implementation in directory /cygdrive/c/ardupilot/build/fmuv3/libraries/GCS_MAVLink/include/mavlink/v2.0/common
[ 9/10] Processing /cygdrive/c/ardupilot/build/fmuv3/libraries/AP_Scripting/lua_generated_bindings.cpp,/cygdrive/c/ardupilot/build/fmuv3/libraries/AP_Scripting/lua_generated_bindings.h: libraries/AP_Scripting/generator/description/bindings.desc build/fmuv3/gen-bindings -> build/fmuv3/libraries/AP_Scripting/lua_generated_bindings.cpp build/fmuv3/libraries/AP_Scripting/lua_generated_bindings.h
Error (line 2): Expected a keyword, got:

Generating C implementation in directory /cygdrive/c/ardupilot/build/fmuv3/libraries/GCS_MAVLink/include/mavlink/v2.0/uAvionix
Generating C implementation in directory /cygdrive/c/ardupilot/build/fmuv3/libraries/GCS_MAVLink/include/mavlink/v2.0/icarous
Copying fixed headers for protocol 2.0 to /cygdrive/c/ardupilot/build/fmuv3/libraries/GCS_MAVLink/include/mavlink/v2.0
Waf: Leaving directory `/cygdrive/c/ardupilot/build/fmuv3’
Build failed
-> task in ‘/cygdrive/c/ardupilot/build/fmuv3/libraries/AP_Scripting/lua_generated_bindings.cpp,/cygdrive/c/ardupilot/build/fmuv3/libraries/AP_Scripting/lua_generated_bindings.h’ failed (exit status 3):
{task 123145247031704: /cygdrive/c/ardupilot/build/fmuv3/libraries/AP_Scripting/lua_generated_bindings.cpp,/cygdrive/c/ardupilot/build/fmuv3/libraries/AP_Scripting/lua_generated_bindings.h bindings.desc,gen-bindings -> lua_generated_bindings.cpp,lua_generated_bindings.h}
(run with -v to display more information)

I’ve just tried with the latest ardupilot and compiled the fmuv3 board with no issues.

Only suggestion I’ve got is to delete and re-download the ardupilot code.

That’s normal. Not an issue.

Thanks, Stephen. I have re-downloaded the code and updated submodules 3 times through git. But it seems no change. I am just wondering if there is something wrong with my cygwin64 installed. However, the packages required are all installed for the latest version in cygwin64. So I am really confused where the problem is.

The copter build also shows ‘No default parameter file found’. Is this normal?

Thanks a lot, Stephen! I reinstall the cygwin64 and ‘git clone’ the code inside the terminal. It shows that the build succeeds. However, when using eclipse, the python version check turns out to be 2.7. And it is certain that there is no packages of ‘pymavlink’ or ‘future’ in it. Therefore, the build fails. To this end, I change the ‘Properties - C/C++ Build - Build command’ as ‘c:\cygwin64\bin\python3.6m waf’ instead of ‘c:\cygwin64\bin\python2.7 waf’. The build is successful. Maybe the instructions in Docs of ‘’ Setup Eclipse on Windows’ on the ardupilot website should be further tested.

Servers by jDrones