Ubuntu 18.04 - gcc-linaro-7.3.1 - "no such file or directory on any tool"

Robotics & Edge Computing Jetson & Embedded Systems Jetson Nano
1

The version of gcc-linaro-7.3.1 provided is behaving strangely on my host Ubuntu 18.04 workstation. I’ve probably done something very silly, but I can’t see what. The files are extracted, they are in user path, they have mode 755, and they show up in bash completion, but when I try to execute any tool, even with ./somebinhere I get

bash: ./aarch64-linux-gnu-foo: No such file or directory

instead of

foo: fatal error: no input files

[user@hostname] -- [~/Dev/nano/l4t-gcc/gcc-linaro-7.3.1-2018.05-i686_aarch64-linux-gnu/bin] 
 $ ls
aarch64-linux-gnu-addr2line  aarch64-linux-gnu-cpp      aarch64-linux-gnu-gcc-7.3.1   aarch64-linux-gnu-gcov-dump  aarch64-linux-gnu-ld       aarch64-linux-gnu-objdump  aarch64-linux-gnu-strip
aarch64-linux-gnu-ar         aarch64-linux-gnu-dwp      aarch64-linux-gnu-gcc-ar      aarch64-linux-gnu-gcov-tool  aarch64-linux-gnu-ld.bfd   aarch64-linux-gnu-ranlib
aarch64-linux-gnu-as         aarch64-linux-gnu-elfedit  aarch64-linux-gnu-gcc-nm      aarch64-linux-gnu-gdb        aarch64-linux-gnu-ld.gold  aarch64-linux-gnu-readelf
aarch64-linux-gnu-c++        aarch64-linux-gnu-g++      aarch64-linux-gnu-gcc-ranlib  aarch64-linux-gnu-gfortran   aarch64-linux-gnu-nm       aarch64-linux-gnu-size
aarch64-linux-gnu-c++filt    aarch64-linux-gnu-gcc      aarch64-linux-gnu-gcov        aarch64-linux-gnu-gprof      aarch64-linux-gnu-objcopy  aarch64-linux-gnu-strings
[user@hostname] -- [~/Dev/nano/l4t-gcc/gcc-linaro-7.3.1-2018.05-i686_aarch64-linux-gnu/bin] 
 $ ./aarch64-linux-gnu-gcc
bash: ./aarch64-linux-gnu-gcc: No such file or directory
[user@hostname] -- [~/Dev/nano/l4t-gcc/gcc-linaro-7.3.1-2018.05-i686_aarch64-linux-gnu/bin] 
 $ gcc
gcc: fatal error: no input files
compilation terminated.

Any ideas would be very much appreciated.

2

I think the very silly thing I may have done is use an unsupported version of the toolchain. I think I found this version in the documentation somewhere but I can’t find it now anymore. Anyway, i’ll try another and that’ll probably solve it.

3

Yeah, it was broken binaries. an unsupported installation configuration. Correct installation of the toolchain requires sudo tar xpf ${L4T_RELEASE_PACKAGE}. It does make sense they would have to be re-linked to work I guess. I found pre-built versions installed via the SDK manager in /usr/bin so it wasn’t even necessary to install it separately.