Arm linux androideabi gcc error

[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

Источник

arm-linux-androideabi-gcc: Internal error: Killed (program cc1) from Android NDK r8

When I build hello-jni which i got from the sample folder of android-ndk-r5, I got a folloiwng error. Would you please tell me your any idea what i missed?

• OS: Ubuntu 10.04 Desktop on WINDOWS 7 via VertualBox
• Android SDK: r08
• Android NDK: r5

detail of error:

5 Answers 5

This error went away for me when I used «make» instead of the recommended «make -j4».

I reformed the detail i posted above.

$ ndk-build
Gdbserver : [arm-linux-androideabi-4.4.3] libs/armeabi/gdbserver
Gdbsetup : libs/armeabi/gdb.setup
Compile thumb : hello-jni

I also had this problem with Ubuntu 10.04 32-bit. I had plenty of disk space on all partitions.

It disappeared after I upgraded to Ubuntu 10.10

I had this problem in my Ubuntu 11.4 VMWare machine. I’m not sure what the root of the issue is.

But rebooting the virtual machine seems to fix the problem for me.

For those having this issue with VMs, the solution that worked for me was bumping up the base memory. It was originally set to 512MB to 1536MB. I’m sure it doesn’t have to be that much but it certainly helps.

Not the answer you’re looking for? Browse other questions tagged android android-ndk or ask your own question.

Related

Hot Network Questions

Subscribe to RSS

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

site design / logo © 2021 Stack Exchange Inc; user contributions licensed under cc by-sa. rev 2021.10.8.40416

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

Источник

arm-linux-androideabi-gcc is unable to create an executable — compile ffmpeg for android armeabi devices

I am trying to compile ffmpeg for android armeabi devices.
I am following tutorial by roman10.net
His given build script builds ffmpeg for armv7-a devices. I want to build it for armeabi.

My ultimate aim is to run ffmpeg commands on android armeabi and armv7-a devices.

So I change the script’s CPU part from

(I thought changing it to armv6 would build ffmpeg compatible with armeabi devices. m I wrong?)

Doubt 1:
Do I also have to change toolchain?
i.e from arm-linux-androideabi-4.4.3 to arm-eabi-4.4.0 .

Doubt 2:

When I try running ./build.sh (without changing toolchain) it gives me following error:

after that I got lot of warnings saying:
‘sub_id’ is deprecated and many other function deprecated warnings.

platform: ubuntu 11.10
ffmpeg version: 0.11.2
NDK : android-ndk-r5b

Here is my build script:

How do I tackle this problem? what is going wrong?

4 Answers 4

I finally found the problem with my setup when facing this same issue. Looking at the arm-build.sh script, I started following the script. Notice the «TOOLCHAIN=. » path.

Originally the path was: TOOLCHAIN= echo $NDK/toolchains/arm-linux-androideabi-4.6/prebuilt/*-x86

When I went to verify this path exists, I noticed that it did not. I think the reason is that I have a 64-bit build.

My path is actually: . /toolchains/arm-linux-androideabi-4.6/prebuilt/linux-x86_64

What I ended up doing was copying the folder, and renaming it to «linux-x86» and now all is compiling.

Hope this helps someone!

I’m not sure if this is what you are looking but I created a script in order to build FFmpeg 0.11.1 for Android. I modified the scripts provided with older Bambuser FFmpeg builds in order to get them working with 0.11.1. I’m currently using this script to build FFmpeg in my own application so I know the build works. The script located at http://servestream.sourceforge.net/build-ffmpeg.sh. I’m using android-ndk-r8b and Ubuntu 12.04 (x64) to do the building. In order to use the script do the following:

1.) Download the script
2.) Open the script and modify the PACKAGE variable to match application’s package
3.) Make it executable: chmod +x build-ffmpeg.sh
4.) Set the NDK variable used by the script, for example: export NDK=/home/user/android-ndk-r8b
5.) Run the script: ./build-ffmpeg.sh

The compiled binaries will be located in the newly created «final-builds» folder in the current working directory. (Note: the script builds binaries for armeabi, armeabi-v7a and x86 architectures)

Источник

arm-linux-androideabi-gcc: error #307

Comments

prestb commented Mar 16, 2016

I am getting the same error:

arm-linux-androideabi-gcc: error: x86_64: No such file or directory arm-linux-androideabi-gcc: error: unrecognized command line option ‘-arch’ error: command ‘arm-linux-androideabi-gcc’ failed with exit status 1 Command failed: ./distribute.sh -m «kivy»

I’m using osx 10.8.5 and have the latest buildozer installed from the github page. Any help appreciated!

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

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

inclement commented Mar 16, 2016

Apparently your NDK doesn’t have the x86_64 build tools, I think you probably need a newer one. Are you using the android_new target, but downloaded the NDK some time ago? If so (or maybe even if you downloaded recently), I think buildozer just isn’t aware of these dependencies yet.

prestb commented Mar 16, 2016

I am using a recent version of NDK == r11 and i was surprised when the error popped up.
Please is there any fix to this?

kived commented May 8, 2016

Please try using the android_new target — i.e. buildozer android_new debug deploy run logcat

awhobbs commented May 2, 2018 •

I’m getting the same error, but just downloaded the latest version of Crystax NDK (using python 3.5).

arm-linux-androideabi-gcc: error: x86_64: No such file or directory arm-linux-androideabi-gcc: error: unrecognized command line option ‘-arch’ error: command ‘arm-linux-androideabi-gcc’ failed with exit status 1

Apparently android_new is now android , so it seems that is not the solution in this case. Any ideas?

Further details:
I’m on OSX 10.11.16 and downloaded buildozer according to these instructions (for python 3).

AndreMiras commented Jun 19, 2018

Could you please share the complete log? For example in my case I had the issue running buildozer in docker container that didn’t have the file binary. First error was:

And that’s why I then had the second error you describe when trying to compile SDL:

So unless you share the complete log it’s hard to help.

awhobbs commented Jun 20, 2018

Sorry about that — I should have shared the complete log. Unfortunately, I no longer have it.

I managed to circumvent the problem by switching to Python 2 (my code only required a few changes). So though that’s a kind of unsatisfying fix it may be a relatively easy solution if someone gets this error again.

Источник

Bambuser ffmpeg — «arm-linux-androideabi-gcc is unable to create an executable file.»

I know this may be possible duplicate of some questions. but answers for those threads are not helping me.

I am trying to compile ffmpeg library for android using Bambuser’s ffmpeg.
I downloaded Archive for client versions 1.3.7 to 1.6.0. from bambuser.

I followed instruction given in REAME.
While running ./build.sh i came across following error

Here are last few lines of config.log of ffmpeg

in tmp i do not find any relative folder or file as per config.log says «ffconf.qflVj27Q.c».

I am doing this on
1. Ubuntu 11.10
2. OpenJDK 6
3. android-ndk-r5b

NOte:
I only have API-10 Installed in eclipse. (if it matters :D)

What could be the solution for this?

2 Answers 2

I finally found the problem with my setup when facing this same issue. Looking at the arm-build.sh script, I started following the script. Notice the «TOOLCHAIN=. » path.

Originally the path was: TOOLCHAIN= echo $NDK/toolchains/arm-linux-androideabi-4.6/prebuilt/*-x86

When I went to verify this path exists, I noticed that it did not. I think the reason is that I have a 64-bit build.

My path is actually: . /toolchains/arm-linux-androideabi-4.6/prebuilt/linux-x86_64

What I ended up doing was copying the folder, and renaming it to «linux-x86» and now all is compiling.

Источник