I have norrowed the error down to this from a larger script and I'm getting the error "No such file or directory" when I try to execute a file which exist and I have the correct permissions for.

fabe@devweb:~$ ls -la /usr/local/android-sdk-linux/build-tools/22.0.0/aapt
-rwxr-xr-x 1 fabe fabe 1264873 Mar 17 10:12 /usr/local/android-sdk-linux/build-tools/22.0.0/aapt
fabe@devweb:~$ /usr/local/android-sdk-linux/build-tools/22.0.0/aapt
-bash: /usr/local/android-sdk-linux/build-tools/22.0.0/aapt: No such file or directory
  • is aapt a script? and something it is trying to open internally is not available?
    – rob
    Mar 23, 2015 at 15:29
  • try sh /usr/local/android-sdk-linux/build-tools/22.0.0/aapt, and if that fails, put a sudo on the front. you may be losing read on the path leading up to the file. Mar 23, 2015 at 15:31
  • It seems to be a binary file. Mar 23, 2015 at 15:32
  • Frank Thomas, that does in fact give a different output indicating it may be a permission problem. Mar 23, 2015 at 15:34

1 Answer 1


As described in this question the common issue may come from missing x86_32 libraries on x64 environment:

sudo apt-get install ia32-libs

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .