USC-ACTLab / crazyswarm

A Large Quadcopter Swarm
MIT License
326 stars 319 forks source link

./build.sh error #171

Closed Allenhanbo closed 5 years ago

Allenhanbo commented 5 years ago

After I Installed the dependencies and cloned the repository into my workspace, then I run the ./build.sh, I meet some error like this:

./build.sh arm-none-eabi-size cf2_nrf.elf text data bss dec hex filename 27320 452 2656 30428 76dc cf2_nrf.elf S110 Activated BLE Disabled Built for platform cf2 CLEAN_VERSION CC usddeck.o src/deck/drivers/src/usddeck.c: In function 'f_gets_without_comments': src/deck/drivers/src/usddeck.c:239:5: error: array subscript has type 'char' [-Werror=char-subscripts] if (isspace(c)) { ^ cc1: all warnings being treated as errors tools/make/targets.mk:26: recipe for target 'usddeck.o' failed make[1]: [usddeck.o] Error 1 Makefile:338: recipe for target 'build' failed make: [build] Error 2

whoenig commented 5 years ago

Your compiler for building the firmware is too old. You can find a newer compiler at https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm/downloads. (Make sure to uninstall the previous compiler version before installing the new one.)

Allenhanbo commented 5 years ago

Hi, thanks for replying me. Could you provide the command to uninstall the previous complier version? I searched for a while, but I didn't find a right to uninstall it.

whoenig commented 5 years ago

Depends on how you installed it. sudo apt-get remove gcc-arm-none-eabi or sudo apt-get remove gcc-arm-embedded on Ubuntu should do the trick.

Allenhanbo commented 5 years ago

Thank you so much! I've already delete the old one. I download the newest version pack from the website you provide. After I unpacked the download, I can not open the arm-none-eabi-gcc file like this: hc@hc-Lenovo:~/gcc-arm-none-eabi-8-2019-q3-update/bin$ arm-none-eabi-gcc arm-none-eabi-gcc: fatal error: no input files compilation terminated.

whoenig commented 5 years ago

That's normal. You need to follow the readme.txt in the archive for installation instructions. Once successfully installed, ./build.sh should run successfully.

Allenhanbo commented 5 years ago

Thanks I've already build successfully.