Question

4

Why can't I run any Android NDK commands?

rated 0 times [ 4] [ 0] / answers: 1 / hits: 5575 / 1 Year ago, thu, february 16, 2023, 5:09:20

I had been running Mint 12 before, and everything was working there. I switched to Ubuntu 12.04, and now I am very frustrated.

When I run ndk-build, I get

/home/buzz/ndk/prebuilt/linux-x86/bin/make: not found

So, I changed to that folder directly. When I type in ./make, I get

bash: ./make: No such file or directory

Typing ls clearly shows the file where I am! I did some hacking around (pointing to external tools) to get past each error (just to experiment), and I ran into this!

/home/buzz/ndk/toolchains/arm-linux-androideabi-4.6/prebuilt/linux-x86/bin/arm-linux-androideabi-gcc: Command not found

Why? Why are all these files unable to be found? As I said above, this was all working just fine in another distro. What changed? What's extra frustrating is that if I push TAB to auto-complete, it works. So, the file is clearly there (and clearly marked with execution permissions). So, why can't it be found?

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

aciousoun

Add To Favorites

Follow

Total Points: 178

Total Questions: 110

Total Answers: 98

Location: Lithuania

Member since Fri, Sep 4, 2020

4 Years ago

aciousoun questions

1 How can I store the IP and Port that are separated by ":" to two variables?

Sat, May 27, 23, 02:24, 1 Year ago

1 Ubuntu 20.04 won't wake from suspend or completely shutdown

Wed, Apr 6, 22, 20:05, 2 Years ago

1 20.04 sudo apt update is showing the error: http://ddebs.ubuntu.com focal-security Release 404 Not Found

Sat, Mar 12, 22, 04:10, 2 Years ago

1 File Location in Hard Disks

Sat, Aug 14, 21, 14:40, 3 Years ago

1 Thunderbird "Open Message in Conversation" sometimes opens different thread

Wed, Apr 20, 22, 08:59, 2 Years ago

View All

answered 1 Year ago ticrew · Accepted Answer

I found the answer.

I installed ia32-libs, and everything started working. It's bizarre that running an executable of the wrong architecture results in "command not found". I was trying all the wrong things.