Problem with setting up SITL on window

mingcheng · July 20, 2019, 8:22am

Hi, I followed the instructions on http://ardupilot.org/dev/docs/sitl-native-on-windows.html, than proceed to this page, http://ardupilot.org/dev/docs/building-setup-windows-cygwin.html#building-setup-windows-cygwin. Everything goes find but I stuck on “Build with Waf” stage.
When I finish installing waf base on https://waf.io/book/#_getting_the_waf_file, and I install it under C:\cygwin64\home\abc\ardupilot. However, when I key in the lines below into Cygwin(x64)
$ cd ~/ardupilot
$ python waf
the error message is:
Waf: Entering directory /home/abc/ardupilot/build' [1/1] Creating waf -> preparing 'tmp-waf-2.0.18' Waf: Leaving directory/home/abc/ardupilot/build’
Build failed
Traceback (most recent call last):
File “/home/abc/ardupilot/.waf-2.0.18-96675f149f50dab16c9e2e6aaf5e787b/waflib/Task.py”, line 350, in process
ret = self.run()
File “/home/abc/ardupilot/wscript”, line 262, in create_waf
for node in up_node.find_dir(‘waflib’).ant_glob(incl=[’.py’, 'Tools/.py’, ‘extras/*.py’]):
AttributeError: ‘NoneType’ object has no attribute ‘ant_glob’
I am unable to build and I am unable to ./waf configure --board Pixhawk1.
When I tried to type: ./waf configure --board Pixhawk1, I have the feedback below:
waf [commands] [options]

Main commands (example: ./waf build -j4)
build : executes the build
clean : cleans the project
configure: configures the project
dist : makes a tarball for redistributing the sources
distcheck: checks if the project compiles (tarball from ‘dist’)
distclean: removes build folders and data
install : installs the targets on the system
list : lists the targets to execute
step : executes tasks in a step-by-step fashion, for debugging
uninstall: removes the targets installed

Options:
–version show program’s version number and exit
-c COLORS, --color=COLORS
whether to use colors (yes/no/auto) [default: auto]
-j JOBS, --jobs=JOBS amount of parallel jobs (8)
-k, --keep continue despite errors (-kk to try harder)
-v, --verbose verbosity level -v -vv or -vvv [default: 0]
–zones=ZONES debugging zones (task_gen, deps, tasks, etc)
-h, --help show this help message and exit
–make-waf creates the waf script
–interpreter=INTERPRETER
specify the #! line on top of the waf file
–sign make a signed file
–zip-type=ZIP specify the zip type [Allowed values: bz2 gz xz]
–make-batch creates a convenience waf.bat file (done automatically
on win32 systems)
–set-version=SETVER sets the version number for waf releases (for the
maintainer)
–strip shrinks waf (strip docstrings, saves 33kb)
–nostrip no shrinking
–tools=ADD3RDPARTY Comma-separated 3rd party tools to add, eg:
“compat,ocaml” [Default: “compat15”]
–coretools=CORETOOLS
Comma-separated core tools to add, eg: “vala,tex”
[Default: all of them]
–prelude=PRELUDE Code to execute before calling waf
–namesfrom=NAMESFROM
Obtain the file names from a model archive

Configuration options:
-o OUT, --out=OUT build dir for the project
-t TOP, --top=TOP src dir for the project
–prefix=PREFIX installation prefix [default: ‘/usr/local/’]
–bindir=BINDIR bindir
–libdir=LIBDIR libdir

Build and installation options:
-p, --progress -p: progress bar; -pp: ide output
–targets=TARGETS task generators, e.g. “target1,target2”

Step options:
–files=FILES files to process, by regexp, e.g.
“/main.c,/test/main.o”

Installation and uninstallation options:
–destdir=DESTDIR installation root [default: ‘’]
-f, --force force file installation
–distcheck-args=ARGS
arguments to pass to distcheck

Python Options:
–nopyc Do not install bytecode compiled .pyc files
(configuration) [Default:install]
–nopyo Do not install optimised compiled .pyo files
(configuration) [Default:install]
–nopycache Do not use pycache directory to install objects
[Default:auto]
–python=PYTHON python binary to be used [Default: /usr/bin/python]
–pythondir=PYTHONDIR
Installation path for python modules (py, platform-
independent .py and .pyc files)
–pythonarchdir=PYTHONARCHDIR
Installation path for python extension (pyext, platform-
dependent .so or .dylib files)
waf: error: no such option: --board

May I know is there any one can help with my problem so that I can get my SITL running on windows, thanks a lot.

mingcheng · July 20, 2019, 9:37am

my python is 3.7.4 (64 bit)

TunaLobster · July 20, 2019, 6:59pm

I’ve noticed that there are still a few things in SITL that don’t quite work on Python 3. Python 2.7.x is the way to go for now.

mingcheng · August 6, 2019, 9:47am

Thank you, after I changed to python 2.7 and after I configure the board,(./waf configure --board Pixhawk1) I have no idea why my build failed. (./waf copter)
oOHackFishOo@oOHackFishOo-PC ~/ardupilot
$ ./waf configure --board Pixhawk1
Setting top to : /home/oOHackFishOo/ardupilot
Setting out to : /home/oOHackFishOo/ardupilot/build
Autoconfiguration : enabled
GCOV code coverage analysis : no
Setting board to : Pixhawk1
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’ : no
Checking for cxx flags ‘-MMD’ : no
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
Including /home/oOHackFishOo/ardupilot/libraries/AP_HAL_ChibiOS/hwdef/fmuv3/hwdef.dat
Setup for MCU STM32F427xx
Writing hwdef setup in /home/oOHackFishOo/ardupilot/build/Pixhawk1/hwdef.h
Writing DMA map
Generating ldscript.ld
Checking for env.py
env set BOARD_FLASH_SIZE=2048
env set APJ_BOARD_TYPE=STM32F427xx
env set MAIN_STACK=0x400
env set APJ_BOARD_ID=9
env set HAL_WITH_UAVCAN=1
env set FLASH_RESERVE_START_KB=16
env set CHIBIOS_BUILD_FLAGS=USE_FATFS=yes MCU=cortex-m4 ENV_UDEFS=-DCHPRINTF_USE_FLOAT=1 CHIBIOS_PLATFORM_MK=os/hal/ports/STM32/STM32F4xx/platform.mk CHIBIOS_STARTUP_MK=os/common/startup/ARMCMx/compilers/GCC/mk/startup_stm32f4xx.mk
env set CPU_FLAGS=[’-mcpu=cortex-m4’, ‘-mfpu=fpv4-sp-d16’, ‘-mfloat-abi=hard’, ‘-u_printf_float’]
env set IOMCU_FW=0
env set PROCESS_STACK=0x2000
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 : 2.7.16
Checking for program ‘python’ : /usr/bin/python
Checking for python version >= 2.7.0 : 2.7.16
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 (3.886s)

oOHackFishOo@oOHackFishOo-PC ~/ardupilot
$ ./waf copter
Waf: Entering directory `/home/oOHackFishOo/ardupilot/build/Pixhawk1’
Padded 16 bytes for bootloader.bin
Embedding file sandbox.lua:libraries/AP_Scripting/scripts/sandbox.lua
Embedding file io_firmware.bin:Tools/IO_Firmware/iofirmware_lowpolh.bin
Embedding file bootloader.bin:/home/oOHackFishOo/ardupilot/Tools/bootloaders/Pixhawk1_bl.bin
Checking for env.py
env added BOARD_FLASH_SIZE=2048
env added APJ_BOARD_TYPE=STM32F427xx
env added MAIN_STACK=0x400
env added APJ_BOARD_ID=9
env added HAL_WITH_UAVCAN=1
env added FLASH_RESERVE_START_KB=16
env added CHIBIOS_BUILD_FLAGS=USE_FATFS=yes MCU=cortex-m4 ENV_UDEFS=-DCHPRINTF_USE_FLOAT=1 CHIBIOS_PLATFORM_MK=os/hal/ports/STM32/STM32F4xx/platform.mk CHIBIOS_STARTUP_MK=os/common/startup/ARMCMx/compilers/GCC/mk/startup_stm32f4xx.mk
env appended CPU_FLAGS=[’-mcpu=cortex-m4’, ‘-mfpu=fpv4-sp-d16’, ‘-mfloat-abi=hard’, ‘-u_printf_float’]
env added IOMCU_FW=0
env added PROCESS_STACK=0x2000
[3/8] Creating build/Pixhawk1/hwdef.h
[4/8] Creating build/Pixhawk1/modules/ChibiOS/include_dirs
[5/8] Processing modules/mavlink/message_definitions/v1.0/ardupilotmega.xml
[6/8] Processing uavcangen: libraries/AP_UAVCAN/dsdl/com modules/uavcan/dsdl/uavcan
[7/8] Creating build/Pixhawk1/ap_version.h
Including /home/oOHackFishOo/ardupilot/libraries/AP_HAL_ChibiOS/hwdef/fmuv3/hwdef.dat
Setup for MCU STM32F427xx
Writing hwdef setup in /home/oOHackFishOo/ardupilot/build/Pixhawk1/hwdef.h
Writing DMA map
Generating ldscript.ld

Validation skipped for /home/oOHackFishOo/ardupilot/modules/mavlink/message_definitions/v1.0/ardupilotmega.xml.
Parsing /home/oOHackFishOo/ardupilot/modules/mavlink/message_definitions/v1.0/ardupilotmega.xml
MAV_CMD
MAV_CMD_DO_GRIPPER
MAV_CMD_DO_AUTOTUNE_ENABLE
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_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
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 /home/oOHackFishOo/ardupilot/modules/mavlink/message_definitions/v1.0/common.xml.
Parsing /home/oOHackFishOo/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_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 (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 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 (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 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.
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 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 (174 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 (239 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 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 /home/oOHackFishOo/ardupilot/modules/mavlink/message_definitions/v1.0/uAvionix.xml.
Parsing /home/oOHackFishOo/ardupilot/modules/mavlink/message_definitions/v1.0/uAvionix.xml
Validation skipped for /home/oOHackFishOo/ardupilot/modules/mavlink/message_definitions/v1.0/icarous.xml.
Parsing /home/oOHackFishOo/ardupilot/modules/mavlink/message_definitions/v1.0/icarous.xml
Merged enum MAV_CMD
Found 222 MAVLink message types in 4 XML files
Generating C implementation in directory /home/oOHackFishOo/ardupilot/build/Pixhawk1/libraries/GCS_MAVLink/include/mavlink/v2.0/ardupilotmega
Generating C implementation in directory /home/oOHackFishOo/ardupilot/build/Pixhawk1/libraries/GCS_MAVLink/include/mavlink/v2.0/common
Generating C implementation in directory /home/oOHackFishOo/ardupilot/build/Pixhawk1/libraries/GCS_MAVLink/include/mavlink/v2.0/uAvionix
Generating C implementation in directory /home/oOHackFishOo/ardupilot/build/Pixhawk1/libraries/GCS_MAVLink/include/mavlink/v2.0/icarous
Copying fixed headers for protocol 2.0 to /home/oOHackFishOo/ardupilot/build/Pixhawk1/libraries/GCS_MAVLink/include/mavlink/v2.0
[8/8] Linking build/Pixhawk1/modules/ChibiOS/libch.a
[1/104] ChibiOS: Compiling crt0_v7m.S
[2/104] ChibiOS: Compiling vectors.S
[3/104] ChibiOS: Compiling chcoreasm_v7m.S
[4/104] ChibiOS: Compiling ff.c
[5/104] ChibiOS: Compiling ffunicode.c
[6/104] ChibiOS: Compiling chcore.c
[7/104] ChibiOS: Compiling chcore_v7m.c
[8/104] ChibiOS: Compiling crt1.c
[9/104] ChibiOS: Compiling chprintf.c
[10/104] ChibiOS: Compiling memstreams.c
[11/104] ChibiOS: Compiling nullstreams.c
[12/104] ChibiOS: Compiling osal.c
[13/104] ChibiOS: Compiling hal_adc_lld.c
[14/104] ChibiOS: Compiling hal_can_lld.c
[15/104] ChibiOS: Compiling hal_crypto_lld.c
[16/104] ChibiOS: Compiling hal_dac_lld.c
[17/104] ChibiOS: Compiling stm32_dma.c
[18/104] ChibiOS: Compiling stm32_exti.c
[19/104] ChibiOS: Compiling hal_pal_lld.c
[20/104] ChibiOS: Compiling hal_i2c_lld.c
[21/104] ChibiOS: Compiling hal_mac_lld.c
[22/104] ChibiOS: Compiling hal_usb_lld.c
[23/104] ChibiOS: Compiling hal_wspi_lld.c
[24/104] ChibiOS: Compiling hal_rtc_lld.c
[25/104] ChibiOS: Compiling hal_sdc_lld.c
[26/104] ChibiOS: Compiling hal_i2s_lld.c
[27/104] ChibiOS: Compiling hal_spi_lld.c
[28/104] ChibiOS: Compiling hal_eicu_lld.c
[29/104] ChibiOS: Compiling hal_gpt_lld.c
[30/104] ChibiOS: Compiling hal_icu_lld.c
[31/104] ChibiOS: Compiling hal_pwm_lld.c
[32/104] ChibiOS: Compiling hal_st_lld.c
[33/104] ChibiOS: Compiling hal_serial_lld.c
[34/104] ChibiOS: Compiling hal_uart_lld.c
[35/104] ChibiOS: Compiling hal_wdg_lld.c
[36/104] ChibiOS: Compiling hal_lld.c
[37/104] ChibiOS: Compiling stm32_isr.c
[38/104] ChibiOS: Compiling nvic.c
[39/104] ChibiOS: Compiling hal.c
[40/104] ChibiOS: Compiling hal_adc.c
[41/104] ChibiOS: Compiling hal_buffers.c
[42/104] ChibiOS: Compiling hal_can.c
[43/104] ChibiOS: Compiling hal_crypto.c
[44/104] ChibiOS: Compiling hal_dac.c
[45/104] ChibiOS: Compiling hal_eicu.c
[46/104] ChibiOS: Compiling hal_gpt.c
[47/104] ChibiOS: Compiling hal_i2c.c
[48/104] ChibiOS: Compiling hal_i2s.c
[49/104] ChibiOS: Compiling hal_icu.c
[50/104] ChibiOS: Compiling hal_mac.c
[51/104] ChibiOS: Compiling hal_mmc_spi.c
[52/104] ChibiOS: Compiling hal_mmcsd.c
[53/104] ChibiOS: Compiling hal_pal.c
[54/104] ChibiOS: Compiling hal_pwm.c
[55/104] ChibiOS: Compiling hal_queues.c
[56/104] ChibiOS: Compiling hal_rtc.c
[57/104] ChibiOS: Compiling hal_sdc.c
[58/104] ChibiOS: Compiling hal_serial.c
[59/104] ChibiOS: Compiling hal_serial_usb.c
[60/104] ChibiOS: Compiling hal_sio.c
[61/104] ChibiOS: Compiling hal_spi.c
[62/104] ChibiOS: Compiling hal_st.c
[63/104] ChibiOS: Compiling hal_trng.c
[64/104] ChibiOS: Compiling hal_uart.c
[65/104] ChibiOS: Compiling hal_usb.c
[66/104] ChibiOS: Compiling hal_wdg.c
[67/104] ChibiOS: Compiling hal_wspi.c
[68/104] ChibiOS: Compiling chfactory.c
[69/104] ChibiOS: Compiling chmboxes.c
[70/104] ChibiOS: Compiling chmemcore.c
[71/104] ChibiOS: Compiling chmemheaps.c
[72/104] ChibiOS: Compiling chmempools.c
[73/104] ChibiOS: Compiling chpipes.c
[74/104] ChibiOS: Compiling chcond.c
[75/104] ChibiOS: Compiling chdebug.c
[76/104] ChibiOS: Compiling chdynamic.c
[77/104] ChibiOS: Compiling chevents.c
[78/104] ChibiOS: Compiling chmsg.c
[79/104] ChibiOS: Compiling chmtx.c
[80/104] ChibiOS: Compiling chregistry.c
[81/104] ChibiOS: Compiling chschd.c
[82/104] ChibiOS: Compiling chsem.c
[83/104] ChibiOS: Compiling chstats.c
[84/104] ChibiOS: Compiling chsys.c
[85/104] ChibiOS: Compiling chthreads.c
[86/104] ChibiOS: Compiling chtm.c
[87/104] ChibiOS: Compiling chtrace.c
[88/104] ChibiOS: Compiling chvt.c
[89/104] ChibiOS: Compiling fatfs_diskio.c
[90/104] ChibiOS: Compiling fatfs_syscall.c
[91/104] ChibiOS: Compiling stubs.c
[92/104] ChibiOS: Compiling board.c
[93/104] ChibiOS: Compiling usbcfg.c
[94/104] ChibiOS: Compiling usbcfg_dualcdc.c
[95/104] ChibiOS: Compiling usbcfg_common.c
[96/104] ChibiOS: Compiling flash.c
[97/104] ChibiOS: Compiling malloc.c
[98/104] ChibiOS: Compiling hrt.c
[99/104] ChibiOS: Compiling stm32_util.c
[100/104] ChibiOS: Compiling bouncebuffer.c
[101/104] ChibiOS: Compiling watchdog.c
[102/104] ChibiOS: Compiling posix.c
[103/104] ChibiOS: Compiling ch.cpp
[104/104] ChibiOS: Compiling syscalls_cpp.cpp

ChibiOS: Done!

C:\Program Files (x86)\GNU Tools ARM Embedded\6 2017-q2-update\bin\arm-none-eabi-ar.exe: creating modules/ChibiOS/libch.a

[ 9/609] Compiling libraries/AC_AttitudeControl/AC_AttitudeControl_Sub.cpp
[ 10/609] Compiling libraries/AC_AttitudeControl/AC_AttitudeControl_Heli.cpp
[ 11/609] Compiling libraries/AC_AttitudeControl/ControlMonitor.cpp
[ 12/609] Compiling libraries/AC_AttitudeControl/AC_AttitudeControl_Multi.cpp
Assembler messages:
Fatal error: can’t create /home/oOHackFishOo/ardupilot/build/Pixhawk1/libraries/AC_AttitudeControl/AC_AttitudeControl_Sub.cpp.0.o: No such file or directory

Assembler messages:
Fatal error: can’t create /home/oOHackFishOo/ardupilot/build/Pixhawk1/libraries/AC_AttitudeControl/AC_AttitudeControl_Heli.cpp.0.o: No such file or directory

Assembler messages:
Fatal error: can’t create /home/oOHackFishOo/ardupilot/build/Pixhawk1/libraries/AC_AttitudeControl/ControlMonitor.cpp.0.o: No such file or directory

Assembler messages:
Fatal error: can’t create /home/oOHackFishOo/ardupilot/build/Pixhawk1/libraries/AC_AttitudeControl/AC_AttitudeControl_Multi.cpp.0.o: No such file or directory

Waf: Leaving directory `/home/oOHackFishOo/ardupilot/build/Pixhawk1’
Build failed
-> task in ‘objs/AC_AttitudeControl’ failed with exit status 1 (run with -v to display more information)
-> task in ‘objs/AC_AttitudeControl’ failed with exit status 1 (run with -v to display more information)
-> task in ‘objs/AC_AttitudeControl’ failed with exit status 1 (run with -v to display more information)
-> task in ‘objs/AC_AttitudeControl’ failed with exit status 1 (run with -v to display more information)
Please any one can help me on this.
Thank you very much

TunaLobster · August 9, 2019, 6:56pm

Why are you configuring for a Pixhawk 1 board? From https://github.com/ArduPilot/ardupilot/blob/master/BUILD.md it should be ./waf configure --board sitl.