bash: adb: command not found.

manuelschneid3r · 2013-04-22 18:20:00

I installed ADT bundle from Google.
I navigated to

~/adt-bundle-linux-x86_64-20130219/sdk/platform-tools

I tried to start adb and got.

bash: adb: command not found.

Grrrrr. Had this issue on Debian half a year before. Installed ia32-libs back-then. It worked.
Arch has no ia32-libs. Uncommented multilib and installed

lib32-gcc-libs-4.8.0-2  lib32-glibc-2.17-5  lib32-libstdc++5-3.3.6-6  lib32-ncurses-5.9-2

Like suggested in the forum. No change. Adb is still not found.

Any help?

Last edited by manuelschneid3r (2013-04-22 18:21:58)

65kid · 2013-04-22 18:26:43

why not just use the AUR packages?

drcouzelis · 2013-04-22 18:29:05

Ah, adb! I thought I recognized that command. You're doing Android development type stuff, right?

manuelschneid3r wrote:

I tried to start adb and got.
bash: adb: command not found.

...if you can see the "adb" application in the current directory, doesn't that just mean you need to type "./adb"?

EDIT: Also, I installed it using the AUR packages, for what it's worth.

Last edited by drcouzelis (2013-04-22 18:29:54)

cookies · 2013-04-22 18:33:55

drcouzelis wrote:

...if you can see the "adb" application in the current directory, doesn't that just mean you need to type "./adb"?

Unless of course you feel the very strong desire to use absolute paths

manuelschneid3r · 2013-04-22 18:50:47

Well I am used to it. I installed ADT Bundle on Win, Ubuntu, Debian always from the Webpage... Okay, does the AUR version work out of the box? Is it up to date?

Yes Android devel stuff. Quite fun.

greets

Last edited by manuelschneid3r (2013-04-22 18:51:06)

drcouzelis · 2013-04-22 18:52:49

manuelschneid3r wrote:

Well I am used to it. I installed ADT Bundle on Win, Ubuntu, Debian always from the Webpage... Okay, does the AUR version work out of the box? Is it up to date?

Well, sure, the AUR just downloads the same Zipped file that you downloaded, but...

Are you actually running the binary, liked I asked about above? ("./adb")

EDIT: Because you obviously have experience with Linux (Ubuntu, Debian...), so I feel silly asking such a simple question, but the error message "command not found" really just sounds like you're not telling Bash which application to run. Are you familiar with the difference between "adb" and "./adb" and why it's important?

Last edited by drcouzelis (2013-04-22 18:56:53)

manuelschneid3r · 2013-04-22 18:54:05

Yes, I tried it exactly this way.

drcouzelis · 2013-04-22 19:00:57

manuelschneid3r wrote:

Yes, I tried it exactly this way.

OK, are you running it from the directory that contains the "adb" application? What are the permissions of the "adb" file?

Also, please see my question in the "EDIT" above.

manuelschneid3r · 2013-04-22 19:12:44

I tried a lot distros, but I still would not call me an advanced user. I dont know exactly the dfference but ./foo runs something that has rights to be executed. Yes I called it in the right directory. Its a linking problem. (See here)

I installed the dependencies of android from AUR. Now it works but it shows ??????????? as device...

Incredibly sick, that Android SDK is not in the official repos...

Last edited by manuelschneid3r (2013-04-22 19:22:51)

HalosGhost · 2013-04-22 19:38:11

manuelschneid3r wrote:

I tried a lot distros, but I still would not call me an advanced user. I dont know exactly the dfference but ./foo runs something that has rights to be executed. Yes I called it in the right directory. Its a linking problem. (See here)
I installed the dependencies of android from AUR. Now it works but it shows ??????????? as device...
Incredibly sick, that Android SDK is not in the official repos...

The "????????????" means that you do not have the correct udev rules setup. There's an adb udev rules package to install to get around having to write your own.

And no, `./script.sh` executes something in the present working directory. It is equivalent to:

$ $SHELL $(pwd)/script.sh

All the best,

-HG

drcouzelis · 2013-04-22 19:41:45

manuelschneid3r wrote:

I called it in the right directory. Its a linking problem. (See here)

I see! I learned something new. Thank you.

opt1mus · 2013-04-22 19:55:49

If you're getting a string of erotemes instead of a device name, this can sometimes be solved by killing and restarting the server;

# adb kill-server
# adb start-server

then query the devices again.

Arch Linux

#1 2013-04-22 18:20:00

bash: adb: command not found.

#2 2013-04-22 18:26:43

Re: bash: adb: command not found.

#3 2013-04-22 18:29:05

Re: bash: adb: command not found.

#4 2013-04-22 18:33:55

Re: bash: adb: command not found.

#5 2013-04-22 18:50:47

Re: bash: adb: command not found.

#6 2013-04-22 18:52:49

Re: bash: adb: command not found.

#7 2013-04-22 18:54:05

Re: bash: adb: command not found.

#8 2013-04-22 19:00:57

Re: bash: adb: command not found.

#9 2013-04-22 19:12:44

Re: bash: adb: command not found.

#10 2013-04-22 19:38:11

Re: bash: adb: command not found.

#11 2013-04-22 19:41:45

Re: bash: adb: command not found.

#12 2013-04-22 19:55:49

Re: bash: adb: command not found.

Board footer