Arm linux androideabi gcc команда не найдена

[question] arm-linux-androideabi-gcc: not found | Error 127, Error 2, #1321

Comments

LovableFatty commented Jul 21, 2020

Steps I followed:
make ARCH=arm goldfish_armv7_defconfig
make ARCH=arm menuconfig
check «enable loadable module support»
check «module unloading»
make ARCH=arm SUB_ARCH=arm CROSS_COMPILE=$/home/noah/Downloads/prebuilt-darwin/darwin-x86/toolchain/arm-linux-androideabi-4.4.x/bin/arm-linux-androideabi-

The text was updated successfully, but these errors were encountered:

LovableFatty commented Jul 21, 2020

It states arm-linux-androideabi-gcc: not found but going into the file shows arm-linux-androideabi-gcc

stephenhines commented Jul 21, 2020

It looks like you’re trying to build the Linux kernel with some NDK prebuilts that you have, but you really need to supply us with more information before we can help here. I’m also going to point out that you need to be building the Linux kernel with Clang instead of gcc, as we no longer provide support for gcc in the Android toolchain. @nickdesaulniers, can you post a sample command line for your suggested kernel build?

stephenhines commented Jul 21, 2020

Actually, I just spotted your bug. $/home/noah/Downloads/prebuilt-darwin/darwin-x86/toolchain/arm-linux-androideabi-4.4.x/bin/arm-linux-androideabi- in your command line should probably be $HOME/Downloads/. or just drop the $ from that part of your command line.

LovableFatty commented Jul 21, 2020 •

Actually, I just spotted your bug. $/home/noah/Downloads/prebuilt-darwin/darwin-x86/toolchain/arm-linux-androideabi-4.4.x/bin/arm-linux-androideabi- in your command line should probably be $HOME/Downloads/. or just drop the $ from that part of your command line.

Tried both solutions and didn’t work

DanAlbert commented Jul 21, 2020

The NDK doesn’t have GCC 4.4. The path you’re using isn’t pointing at a real directory.

LovableFatty commented Jul 21, 2020

The NDK doesn’t have GCC 4.4. The path you’re using isn’t pointing at a real directory.

Doesn’t this image showcase gcc 4.4.3? Also what do you mean by ‘The path you’re using isn’t pointing at a real directory.’ ?

LovableFatty commented Jul 21, 2020 •

building the Linux kernel with Clang
@stephenhines
After I build a linux kernel with clang how do I build an android LKM? that’s my end goal

DanAlbert commented Jul 21, 2020

That’s an extremely old NDK then.

stephenhines commented Jul 21, 2020

building the Linux kernel with Clang
@stephenhines
After I build a linux kernel with clang how do I build an android LKM? that’s my end goal

Источник

linux-x86/bin/arm-linux-androideabi-gcc: Command not found #146

Comments

smaznet commented Jul 3, 2016

i have this error with ndk 11

and I am using ubuntu 16.04 x86

and linux-x86 for not availiable in prebuilt folder i also coppied and renamed linux-x86_x64
to linux-x86 but i got a new error

The text was updated successfully, but these errors were encountered:

smaznet commented Jul 3, 2016

This is my error in android studio

DanAlbert commented Jul 6, 2016

and I am using ubuntu 16.04 x86

32-bit Linux is no longer supported. You’ll have the same issue with new versions of the SDK tools as well.

jk2K commented Sep 2, 2016

I am using Debian 8 x86_64,

I have this error with android-ndk-r12b

I have linux-x86_64 directory

What should I do ?

bertrandmartel commented Oct 3, 2016

I had this issue in a docker container. file command was missing as you can see from the error file: not found .

In android-ndk-root/build/core/init.mk , the architecture is checked with file -L /bin/sh | grep ‘x86[_-]64’ so if file is missing it chooses the default x86

DanAlbert commented Oct 3, 2016

This comment was marked as off-topic.

LovableFatty commented Jul 23, 2020

i have this error with ndk 11

and I am using ubuntu 16.04 x86

and linux-x86 for not availiable in prebuilt folder i also coppied and renamed linux-x86_x64
to linux-x86 but i got a new error

Having the same issue with NDK r18b. did you ever fix it?

stephenhines commented Jul 23, 2020

The issue above is because you’re missing a / in front of the home in your commands. It’s looking for home/. instead of /home/. , which is why it can’t find the tools.

LovableFatty commented Jul 23, 2020

The issue above is because you’re missing a / in front of the home in your commands. It’s looking for home/. instead of /home/. , which is why it can’t find the tools.

tried /home/ & HOME/ & /HOME/

stephenhines commented Jul 23, 2020

The errors are actually showing you what is wrong. You need to make this $HOME/Downloads/. or /home/noah/Downloads/. . You keep adjusting it to something else that expands incorrectly.

LovableFatty commented Jul 23, 2020

The errors are actually showing you what is wrong. You need to make this $HOME/Downloads/. or /home/noah/Downloads/. . You keep adjusting it to something else that expands incorrectly.

Thanks for taking the time to explain it to me.

Any idea what I can do to fix these errors?

stephenhines commented Jul 23, 2020

I think that those are GCC-specific flags that don’t do anything with Clang. See #111 (comment) for where I’ve answered this before. Somewhere you must be passing these flags to Clang directly (either on purpose or by accident).

LovableFatty commented Jul 23, 2020

I think that those are GCC-specific flags that don’t do anything with Clang. See #111 (comment) for where I’ve answered this before. Somewhere you must be passing these flags to Clang directly (either on purpose or by accident).

I realized I wrote my make line wrong by having SUB_ARM=arm instead of SUB_ARCH=arm
My current error is the same as before.

stephenhines commented Jul 24, 2020

You’re working as root in the last message. You want to go back to your regular user account. It’s expanding $HOME to /root/ when you’re running as root, which isn’t where your tools live (back in the noah home dir).

LovableFatty commented Jul 24, 2020 •

You’re working as root in the last message. You want to go back to your regular user account. It’s expanding $HOME to /root/ when you’re running as root, which isn’t where your tools live (back in the noah home dir).

current problem. resolved the clang input issue by taking out a line according to #111. Tried a solution from where I change the kbuild and kbuild.h http://patchwork.ozlabs.org/project/uboot/patch/1406750096-7281-7-git-send-email-jeroen@myspectrum.nl/
but it resulted in error as well

Источник

Android NDK — arm-linux-androideabi-g++: not found

I am trying to build the C++ POCO library for an Android target in a fresh Ubuntu that I just installed for that.

I have installed the Android NDK in /home/user/dev/Android/android-ndk-r9-x86 and added the path to the NDK in the environement variables using :

To build the libraries I first move to the root directory of the POCO library, and configure it using :

So that it compiles static .a libraries, doesn’t compile the modules I don’t want and compiles for an Android target.

But than calling make causes the following error :

Make seems unable to find the compiler used for Android, and I have no idea why ? What am I missing ? Did i forget something when «installing» the NDK ?

1 Answer 1

The error you’re getting is caused by a missing toolchain invocation — rather, the arm-linux-androideabi-g++ command/executable/binary was nowhere to be found.

Luckily, we can get around that by installing the Standalone toolchain — that one actually has the exact thing you’re missing, a general purpose arm-linux-androideabi cross-compiler instead of some other, a bit more obscure, vendor/platform-specific crosscompiler/toolchain, such as armv7a-marvell-linux-android which is what marvell uses, or arm-linux-android which is what Clang uses. For more info on Clang, look here. I could be wrong though and that Clang actually produces a arm-linux-androideabi toolchain out of the box, but I’m unsure. I know you can use it easily, I’m just unsure if it can be used «straight out of the box» which is what you’re looking for. The «rest of the work» is just a few path exports — but still. We’re aiming for the laziest solution here.

The standalone toolchain should be quite sufficient for your task, so try using it as much as possible over any other cross-compilation solutions.

However, if you’re feeling adventurous — you’re free to make your own cross-compiler (or the whole toolchain!) using the crosstool-ng tool. However, try to stick with the Linaro libc branch; personal experience showed me that one somehow works the best and causes the least amount of problems/time wasted.

Also, make sure you download the right one for your architecture (arch) and OS, 32bit vs 64bit matters here as well. After a lengthy discussion, we realized it was a «32bit vs 64bit» problem. Here’s a link to read more about it.

Источник

Arm-linux-androideabi-gcc не может создать исполняемый файл – компиляция ffmpeg для устройств android armeabi

Я пытаюсь скомпилировать ffmpeg для устройств android armeabi.
Я следую учебнику от roman10.net
Его сценарий сборки создает ffmpeg для устройств armv7-a. Я хочу построить его для армейцев.

Моя конечная цель – запустить команды ffmpeg на устройствах android armeabi и armv7-a.

Поэтому я меняю часть процессора на скрипт

(Я думал, что сменить его на armv6 будет строить ffmpeg, совместимый с устройствами armeabi. Я ошибаюсь?)

Сомнение 1:
Нужно ли мне также менять инструментальную цепочку?
Т.е. от arm-linux-androideabi-4.4.3 до arm-eabi-4.4.0 .

Сомнение 2:

Когда я пытаюсь запустить ./build.sh (без изменения инструментальной цепочки), он вызывает следующую ошибку:

После этого у меня появилось много предупреждений:
«Sub_id» устарел и многие другие устаревшие предупреждения.

Платформа : ubuntu 11.10
Версия ffmpeg : 0.11.2
NDK : android-ndk-r5b

Вот мой скрипт сборки:

Как решить эту проблему? Что происходит не так?

Я не уверен, что это то, что вы ищете, но я создал скрипт для создания FFmpeg 0.11.1 для Android. Я изменил скрипты, снабженные старыми сборками Bambuser FFmpeg, чтобы заставить их работать с 0.11.1. В настоящее время я использую этот скрипт для сборки FFmpeg в моем собственном приложении, поэтому я знаю, что сборка работает. Сценарий находится по адресу http://servestream.sourceforge.net/build-ffmpeg.sh . Я использую android-ndk-r8b и Ubuntu 12.04 (x64) для создания здания. Чтобы использовать скрипт, выполните следующие действия:

1.) Загрузите скрипт
2.) Откройте скрипт и измените переменную PACKAGE в соответствии с пакетом приложения
3.) Сделайте его исполняемым: chmod + x build-ffmpeg.sh
4.) Установите переменную NDK, используемую скриптом, например: export NDK = / home / user / android-ndk-r8b
5.) Запустите скрипт: ./build-ffmpeg.sh

Скомпилированные двоичные файлы будут расположены во вновь созданной папке «final-builds» в текущем рабочем каталоге. (Примечание: скрипт создает двоичные файлы для армейских, армейских-v7a и x86-архитектур)

Надеюсь, это ответит на ваш вопрос.

ОБНОВИТЬ:

Я, наконец, нашел проблему с моей настройкой, столкнувшись с этой проблемой … Посмотрев на скрипт arm-build.sh, я начал следовать сценарию. Обратите внимание на путь «TOOLCHAIN ​​= …».

Первоначально путь был следующим: TOOLCHAIN ​​= echo $NDK/toolchains/arm-linux-androideabi-4.6/prebuilt/*-x86

Когда я пошел проверять этот путь, я заметил, что это не так. Я думаю, причина в том, что у меня 64-битная сборка.

Мой путь на самом деле: … / toolchains / arm-linux-androideabi-4.6 / prebuilt / linux-x86_64

То, что я закончил делать, это копирование папки и переименование ее на «linux-x86», и теперь все компилируется.

Надеюсь, это поможет кому-то!

Я получил аналогичную ошибку (тест компилятора C не удался), пытаясь построить ffmpeg, используя версию r8d ndk, а также r8b.

Проблема, которую я позже выяснил, заключается в том, что опция «Извлечь здесь» на последней версии ubuntu, похоже, имеет некоторые ошибки. Он не извлекает все. Таким образом, используя «tar -jxf» извлекает правильно, и вы увидите больше исполняемых файлов в папке bin.

Источник