Hello everyone. I am no stranger to the shell or anything like that, but I just had never come across this behavior before.

I keep a backup of a bunch of files on a flash drive, so that whenever I change distributions I can just restore all my Android stuff (saves on re-downloading everything). One of these is the Android SDK.

In my ~/.bashrc I add the paths to some executables in the SDK, only if the directory exists, and only if the path is not already in $PATH. For the Android NDK this works fine, but for the SDK I get this:
Everything else is fine though, just that one path is causing trouble.

Now, I've saw something similar to this before whenever you move an executable from one place to another. If you don't re-source your bash config it will continue to keep looking wherever it used to be located. But I've never moved these files. Kinda weird.

Anyway, any suggestions on this would be appreciated.

Try ldd /home/snfo/Android/sdk/platform-tools/adb |grep found

Install whatever shows. The correct answer is no output.

Hi,

the only occasion I have observed such behavior is when the executable cannot find its linker. Are you able to run the binary when you call it with full path?
What is the output of
[EDIT]
As already suggested by business kid ...

You guys are right. For some reason it was acting like the binary was not compatible with my system, even though it was the official binary from developer.android.com.

I fixed this by re-compiling adb on my machine.