title: adb doesn't run on Ubuntu 64 - command not found
body: <p><strong>Update</strong></p>
  
  <p>After doing some more experiments, I have to reformulate my question completely as I was fooled by my terminal. It just didn't showed the error message when I issued <strong>sudo ./adb</strong>.</p>
  
  <p>If I cd into the ANDOID_SDK/platform-tools directory and run <strong>./adb</strong>, I get:</p>
  
  <pre><code>command not found: ./adb
  </code></pre>
  
  <p>Here the output <strong>ls -l adb</strong> in the same directory:</p>
  
  <pre><code>-rwxrwxr-x 1 myuser myuser 159620 2011-12-20 19:30 adb
  </code></pre>
  
  <p>Running <strong>which adb</strong> gives me:</p>
  
  <pre><code>./adb
  </code></pre>
  
  <p>The same happens for all other binary executable files in that directory like aapt, aidl, dexdump, etc.</p>
  
  <p>I could just imagine that this has something to do with me trying to run it on a 64bit Ubuntu, but the ELF header or something similar not being recognised. However, the <strong>android</strong> tool in ANDOID_SDK/tools is running fine (besides failing to execute adb after downloading new packages).</p>
  
  <p>Really strange...</p>
  
  <p><strong>Original question</strong></p>
  
  <p>I downloaded the latest Android SDK. If I try running adb as an ordinary user, I get "command not found". I must run it as "sudo ./adb" and it works. Why is that and how do I fix it? I'm running Ubuntu 64 11.10. </p>
  
  <p>I used the SDK on older Ubuntu versions and there, I could run it as ordinary user without problems. Any ideas?</p>