Description
Bug Report
Bug originally mentioned in #292 (comment)
A Vero 4K+ (by OSMC) is a Kodi box which has Debian with aarch64 (arm64) architecture. It's very versatile but it hasn't Xorg installed. It has its own debian repo apt.osmc.tv
and uses the official http://ftp.debian.org/debian stretch main contrib non-free
as well. Yes the stable version is still on Debian Stretch but it's very stable.
It can be accessed on the command line via ssh over Wi-Fi. The default user is named osmc
, who has sudo privileges as well.
Current behavior
installing with the command
curl -fsSL https://raw.githubusercontent.com/arduino/arduino-cli/master/install.sh | sh
I obtain
Installing in /home/osmc/bin
ARCH=ARM64
OS=Linux
Using curl as download tool
TAG=0.13.0
CLI_DIST=arduino-cli_0.13.0_Linux_ARM64.tar.gz
Downloading https://downloads.arduino.cc/arduino-cli/arduino-cli_0.13.0_Linux_ARM64.tar.gz
main: line 204: /home/osmc/bin/arduino-cli: No such file or directory
Failed to install arduino-cli
But the binary /home/osmc/bin/arduino-cli
exists, ergo it's made for the wrong arch, like it was happening in issue 307. I manually installed the arduino-cli
binary from arduino-cli-152-PR307-linuxarm64.tar.bz2 found in a comment there and it works: the output of arduino-cli version
with the 152-PR307 version is
arduino-cli Version: 152-PR307 Commit: 77d5613
and can run other subrutines as well.
I probably could install the 32 bit armhf architeture like suggested online in some places (like here), but it don't like to mess up things and hope for the best. Space is also limited.
It there is a clean solution that you know of, the avr-g++
binary from the main arduino installer has the same problem on this machine (issue 73 on toolchain-avr): running a normal command like arduino-cli compile --fqbn arduino:avr:uno Sketch01
, I'm getting a classic error:
Error: build failed: fork/exec /home/osmc/.arduino15/packages/arduino/tools/avr-gcc/7.3.0-atmel3.6.1-arduino7/bin/avr-g++: no such file or directory
Error during build
avr-g++
exists but it's for the wrong arch for sure (it's typical behaviour with wrong arch binaries). But this problem cannot be solved removing the .arduino15
folder like suggested in many places.