What it's telling you is that a key component of the runtime environment necessary to run the program is missing. The error message in this last case is admittedly confusing.
The file exists, and you can even read it (for example, the command file shank-linux-120720110-1-bin displays something like “ELF 32-bit LSB executable ”), and yet when you try to execute it you're told that the file doesn't exist.There is a file by that name, but it's a dangling symbolic link.I presume you've checked that the file does exist (perhaps because the shell completes it). There are three cases where you can get the message “No such file or directory”: tar.gz ZIPBALL= $PWD/ $BUILD_DIR/ $PACKNAME.zip ZIPEXAMPLE=listdevs-example- $ARCH- $ GITREPO=# Store current dir WORK= $PWD # - TARGET: CLEAN.You're probably trying to run a 32-bit binary on a 64-bit system that doesn't have 32-bit support installed.
$ARCH VERSION=4 PACKNAME= $NAME- $ARCH- $VERSION BUILD_DIR=build_ $ARCH BUILD_DATA=build-data PACK_DIR=packages TARBALL= $PWD/ $BUILD_DIR/ $PACKNAME. Nevertheless, # it is not necesary to compile this library for other programas # The libusb i386 can be obtained with the following command: # sudo apt-get install libusb-1.0:i386 BUILD=x86-unknown-linux-gnu HOST=arm-linux-gnueabihf TARGET=arm-linux-gnueabihf NAME=libusb ARCH=armhf PREFIX= $HOME/. # libusb builder for Ubuntu phone (ARM 32 bits # NOTE: This cross-compilation of the libusb library has been created as an # example of cross-compiling from linux-64 to linux-32. Welcome to the Ubuntu Weekly Newsletter, Issue #1. Ubuntu phone images are built for the target devices below.
Devices - supported and reference devices Supported and reference devices. This only includes the Android Open Source Project. ELF interpreter: No such file or directory.
0 kommentar(er)
