Tiny Core Base > Micro Core

MC 12 x64 -sh: ./adb: not found

(1/4) > >>

Santos:
Hello

https://developer.android.com/studio/releases/platform-tools#downloads

I just recently downloaded the latest version of  adb  from the AOSP project page. In CorePlus with lots of extensions loaded, the binary does runs and I'm able to execute it without any issues.

However, in  microcore  with no extension loaded, I'm getting the   -sh: ./adb: not found   error. I don't know which one is the missing piece in MC.

Typing in: ldd ./adb


--- Code: ---        linux-vdso.so.1 (0x00007ffc56bf3000)
libdl.so.2 => /lib/libdl.so.2 (0x00007f15ed6e5000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00007f15ed6c8000)
libm.so.6 => /lib/libm.so.6 (0x00007f15ed5a4000)
librt.so.1 => /lib/librt.so.1 (0x00007f15ed59b000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007f15ed581000)
libc.so.6 => /lib/libc.so.6 (0x00007f15ed3fd000)
/lib64/ld-linux-x86-64.so.2 => /lib/ld-linux-x86-64.so.2 (0x00007f15eddcb000)

--- End code ---

Any advise?

Thank you.

Rich:
Hi Santos
It's saying that  adb  can not be found in the current directory. Do you see it if you run this command:

--- Code: ---ls -l a*
--- End code ---

If it shows up, see if running this fixes it:

--- Code: ---chmod 775 adb
--- End code ---

Santos:
Hello Rich

Yes,  adb  it is present and permissions are properly set up.


--- Code: ---tc@box:~/Descargas/adb64/platform-tools$ ls -l a*
-rwxr-xr-x    1 tc       staff      8168736 Mar  9 16:20 adb

--- End code ---

What confuses me is that if the file is non-existing the error message is almost the same, but the 'dash' at the beginning is missing.


--- Code: ---sh: ./adc: not found

--- End code ---

Rich:
Hi Santos
Do either of these commands produce a different response:

--- Code: ---./adb --help
./adb help
--- End code ---

Does running this first help:

--- Code: ---hash -r
--- End code ---

Maybe you need to start loading your extensions to see if one of them allows it to work. Openssl, tls, and python
come to mind.

Rich:
Hi Santos
I think this type of error sometimes occurs when bash is needed but not found.

Navigation

[0] Message Index

[#] Next page