New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"No toolchains found in the NDK toolchains folder for ABI with prefix: mips64el-linux-android" #15

Closed
AndroidDeveloperLB opened this Issue Aug 5, 2018 · 55 comments

Comments

Projects
None yet
@AndroidDeveloperLB

AndroidDeveloperLB commented Aug 5, 2018

I just wanted to try out the sample, but I got this error:

image

@romainguy

This comment has been minimized.

Show comment
Hide comment
@romainguy

romainguy Aug 5, 2018

Collaborator

It opens properly for me on several machines. Do you have an NDK properly installed and setup?

Collaborator

romainguy commented Aug 5, 2018

It opens properly for me on several machines. Do you have an NDK properly installed and setup?

@AndroidDeveloperLB

This comment has been minimized.

Show comment
Hide comment
@AndroidDeveloperLB

AndroidDeveloperLB Aug 5, 2018

Isn't this enough:

image

?

AndroidDeveloperLB commented Aug 5, 2018

Isn't this enough:

image

?

@romainguy

This comment has been minimized.

Show comment
Hide comment
@romainguy

romainguy Aug 5, 2018

Collaborator

It should be. I have no idea what the problem is here, we don't even support the MIPS ABI (and it's not part of the NDK anymore I believe).

Collaborator

romainguy commented Aug 5, 2018

It should be. I have no idea what the problem is here, we don't even support the MIPS ABI (and it's not part of the NDK anymore I believe).

@AndroidDeveloperLB

This comment has been minimized.

Show comment
Hide comment
@AndroidDeveloperLB

AndroidDeveloperLB Aug 5, 2018

Is it possible that it's because I'm using Windows OS?
Or that I have AMD CPU ?

AndroidDeveloperLB commented Aug 5, 2018

Is it possible that it's because I'm using Windows OS?
Or that I have AMD CPU ?

@romainguy

This comment has been minimized.

Show comment
Hide comment
@romainguy

romainguy Aug 5, 2018

Collaborator

Those have nothing to do with MIPS so I doubt they're related.

BTW did you follow the other instructions in the README and built the native libraries with cmake already? These are necessary before you can build the AAR.

Collaborator

romainguy commented Aug 5, 2018

Those have nothing to do with MIPS so I doubt they're related.

BTW did you follow the other instructions in the README and built the native libraries with cmake already? These are necessary before you can build the AAR.

@banshee

This comment has been minimized.

Show comment
Hide comment
@banshee

banshee Aug 13, 2018

I had the same problem (a very unexpected "No toolchains found in the NDK toolchains folder for ABI with prefix: mips64el-linux-android") when I opened an old project, and fixed it by updating some build settings:

diff --git a/AndroidStudioHolder/app/build.gradle b/AndroidStudioHolder/app/build.gradle
index c42f8710..8bc8b1aa 100644
--- a/AndroidStudioHolder/app/build.gradle
+++ b/AndroidStudioHolder/app/build.gradle
@@ -2,7 +2,7 @@ apply plugin: 'com.android.application'
 
 android {
     compileSdkVersion 26
-    buildToolsVersion '26.0.2'
+    buildToolsVersion '28.0.2'
 
     defaultConfig {
         applicationId "com.digium.SwitchvoxSoftphone"
diff --git a/AndroidStudioHolder/build.gradle b/AndroidStudioHolder/build.gradle
index 70e20276..8295018f 100644
--- a/AndroidStudioHolder/build.gradle
+++ b/AndroidStudioHolder/build.gradle
@@ -6,7 +6,7 @@ buildscript {
         jcenter()
     }
     dependencies {
-        classpath 'com.android.tools.build:gradle:3.0.1'
+        classpath 'com.android.tools.build:gradle:3.3.0-alpha05'
         classpath 'com.google.gms:google-services:3.1.0'
 
         // NOTE: Do not place your application dependencies here; they belong
diff --git a/AndroidStudioHolder/gradle/wrapper/gradle-wrapper.properties b/AndroidStudioHolder/gradle/wrapper/gradle-wrapper.properties
index 790c9505..4e61a125 100644
--- a/AndroidStudioHolder/gradle/wrapper/gradle-wrapper.properties
+++ b/AndroidStudioHolder/gradle/wrapper/gradle-wrapper.properties
@@ -1,6 +1,6 @@
-#Tue Sep 05 11:15:44 PDT 2017
+#Mon Aug 13 15:32:30 PDT 2018
 distributionBase=GRADLE_USER_HOME
 distributionPath=wrapper/dists
 zipStoreBase=GRADLE_USER_HOME
 zipStorePath=wrapper/dists
-distributionUrl=https\://services.gradle.org/distributions/gradle-4.1-all.zip
+distributionUrl=https\://services.gradle.org/distributions/gradle-4.9-all.zip

banshee commented Aug 13, 2018

I had the same problem (a very unexpected "No toolchains found in the NDK toolchains folder for ABI with prefix: mips64el-linux-android") when I opened an old project, and fixed it by updating some build settings:

diff --git a/AndroidStudioHolder/app/build.gradle b/AndroidStudioHolder/app/build.gradle
index c42f8710..8bc8b1aa 100644
--- a/AndroidStudioHolder/app/build.gradle
+++ b/AndroidStudioHolder/app/build.gradle
@@ -2,7 +2,7 @@ apply plugin: 'com.android.application'
 
 android {
     compileSdkVersion 26
-    buildToolsVersion '26.0.2'
+    buildToolsVersion '28.0.2'
 
     defaultConfig {
         applicationId "com.digium.SwitchvoxSoftphone"
diff --git a/AndroidStudioHolder/build.gradle b/AndroidStudioHolder/build.gradle
index 70e20276..8295018f 100644
--- a/AndroidStudioHolder/build.gradle
+++ b/AndroidStudioHolder/build.gradle
@@ -6,7 +6,7 @@ buildscript {
         jcenter()
     }
     dependencies {
-        classpath 'com.android.tools.build:gradle:3.0.1'
+        classpath 'com.android.tools.build:gradle:3.3.0-alpha05'
         classpath 'com.google.gms:google-services:3.1.0'
 
         // NOTE: Do not place your application dependencies here; they belong
diff --git a/AndroidStudioHolder/gradle/wrapper/gradle-wrapper.properties b/AndroidStudioHolder/gradle/wrapper/gradle-wrapper.properties
index 790c9505..4e61a125 100644
--- a/AndroidStudioHolder/gradle/wrapper/gradle-wrapper.properties
+++ b/AndroidStudioHolder/gradle/wrapper/gradle-wrapper.properties
@@ -1,6 +1,6 @@
-#Tue Sep 05 11:15:44 PDT 2017
+#Mon Aug 13 15:32:30 PDT 2018
 distributionBase=GRADLE_USER_HOME
 distributionPath=wrapper/dists
 zipStoreBase=GRADLE_USER_HOME
 zipStorePath=wrapper/dists
-distributionUrl=https\://services.gradle.org/distributions/gradle-4.1-all.zip
+distributionUrl=https\://services.gradle.org/distributions/gradle-4.9-all.zip

@romainguy romainguy closed this Aug 14, 2018

@AndroidDeveloperLB

This comment has been minimized.

Show comment
Hide comment
@AndroidDeveloperLB

AndroidDeveloperLB Aug 14, 2018

@romainguy You are correct. I was sure it's just NDK that's needed. Seems it's a lot more.
Closing this as I don't have time for this. Sorry.
Thank you for the good work.

AndroidDeveloperLB commented Aug 14, 2018

@romainguy You are correct. I was sure it's just NDK that's needed. Seems it's a lot more.
Closing this as I don't have time for this. Sorry.
Thank you for the good work.

@stark25795

This comment has been minimized.

Show comment
Hide comment
@stark25795

stark25795 Aug 23, 2018

Find your own local android-sdk, if you download the relevant sdk of ndk, there will be a folder called "ndk-bundle"

image

There is a folder called "toolchains" inside.
image

We noticed that there are no mips64el related files inside.
image

The solution is as follows:

Click here to download the NDK package separately through the browser.
After unzipping, open the "toolchains" folder, compare it with the android-sdk->ndk-bundle->toolchains folder, find the missing folder, copy the past
3. Recompile, the problem is solved.
Hope it helps you mate

stark25795 commented Aug 23, 2018

Find your own local android-sdk, if you download the relevant sdk of ndk, there will be a folder called "ndk-bundle"

image

There is a folder called "toolchains" inside.
image

We noticed that there are no mips64el related files inside.
image

The solution is as follows:

Click here to download the NDK package separately through the browser.
After unzipping, open the "toolchains" folder, compare it with the android-sdk->ndk-bundle->toolchains folder, find the missing folder, copy the past
3. Recompile, the problem is solved.
Hope it helps you mate

@AndroidDeveloperLB

This comment has been minimized.

Show comment
Hide comment
@AndroidDeveloperLB

AndroidDeveloperLB Aug 23, 2018

@romainguy Seems "mips64el-linux-android" is missing because it got deprecated:
https://issuetracker.google.com/issues/112810603
https://issuetracker.google.com/issues/112779429

https://developer.android.com/ndk/guides/abis#sa

Note: Historically the NDK supported 32-bit and 64-bit MIPS, but support was removed in NDK r17.

Please avoid using unsupported architectures.

@stark25795 The latest version doesn't have it, because of what I wrote above:
image

AndroidDeveloperLB commented Aug 23, 2018

@romainguy Seems "mips64el-linux-android" is missing because it got deprecated:
https://issuetracker.google.com/issues/112810603
https://issuetracker.google.com/issues/112779429

https://developer.android.com/ndk/guides/abis#sa

Note: Historically the NDK supported 32-bit and 64-bit MIPS, but support was removed in NDK r17.

Please avoid using unsupported architectures.

@stark25795 The latest version doesn't have it, because of what I wrote above:
image

@romainguy

This comment has been minimized.

Show comment
Hide comment
@romainguy

romainguy Aug 23, 2018

Collaborator

That's why we don't support MIPS, because it's been deprecated/removed from the NDK

Collaborator

romainguy commented Aug 23, 2018

That's why we don't support MIPS, because it's been deprecated/removed from the NDK

@AndroidDeveloperLB

This comment has been minimized.

Show comment
Hide comment
@AndroidDeveloperLB

AndroidDeveloperLB Aug 23, 2018

@romainguy So... please remove it from the sample too :)

AndroidDeveloperLB commented Aug 23, 2018

@romainguy So... please remove it from the sample too :)

@romainguy

This comment has been minimized.

Show comment
Hide comment
@romainguy

romainguy Aug 23, 2018

Collaborator

It's not in the samples.

Collaborator

romainguy commented Aug 23, 2018

It's not in the samples.

@AndroidDeveloperLB

This comment has been minimized.

Show comment
Hide comment
@AndroidDeveloperLB

AndroidDeveloperLB Aug 23, 2018

So how did I get this error (look at first post) ?

AndroidDeveloperLB commented Aug 23, 2018

So how did I get this error (look at first post) ?

@mimers

This comment has been minimized.

Show comment
Hide comment
@mimers

mimers Aug 27, 2018

@AndroidDeveloperLB It seems like the old version of android gradle plugin(<3.3.+) was trying to access mips toolchain without checking if it exists. Upgrade the plugin version to 3.3-alpha may adopt to your r18-rc NDK toolchains(as @banshee posted).

mimers commented Aug 27, 2018

@AndroidDeveloperLB It seems like the old version of android gradle plugin(<3.3.+) was trying to access mips toolchain without checking if it exists. Upgrade the plugin version to 3.3-alpha may adopt to your r18-rc NDK toolchains(as @banshee posted).

@AndroidDeveloperLB

This comment has been minimized.

Show comment
Hide comment
@AndroidDeveloperLB

AndroidDeveloperLB Aug 27, 2018

So it's a relatively new issue

AndroidDeveloperLB commented Aug 27, 2018

So it's a relatively new issue

@kles4enko

This comment has been minimized.

Show comment
Hide comment
@kles4enko

kles4enko Aug 27, 2018

for me, upgrade the Android Gradle plugin version to 3.1.3+ works.

kles4enko commented Aug 27, 2018

for me, upgrade the Android Gradle plugin version to 3.1.3+ works.

@chris118

This comment has been minimized.

Show comment
Hide comment
@chris118

chris118 commented Sep 17, 2018

@stark25795 it works for me

@AndroidDeveloperLB

This comment has been minimized.

Show comment
Hide comment
@AndroidDeveloperLB

AndroidDeveloperLB Sep 18, 2018

@chris118 What worked? Which sample worked for you?
I think I tried them all. What did you do?

AndroidDeveloperLB commented Sep 18, 2018

@chris118 What worked? Which sample worked for you?
I think I tried them all. What did you do?

@gatschet

This comment has been minimized.

Show comment
Hide comment
@gatschet

gatschet Sep 19, 2018

For me, just remove tick NUK in SDL tools resolved the problem...

gatschet commented Sep 19, 2018

For me, just remove tick NUK in SDL tools resolved the problem...

@adrianodelvigna

This comment has been minimized.

Show comment
Hide comment
@adrianodelvigna

adrianodelvigna Sep 19, 2018

@AndroidDeveloperLB, I had the same problem with another project. I followed the instructions from Android Plugin for Gradle release notes; you may try to change your Project Structure settings as (check bold for the changes):

  • Gradle version: 4.4
  • Android Plugin Version: 3.1.0
  • Android Plugin Repository: jcenter, google()
  • Default Library Repository: jcenter

image

I resync'ed Gradle then rebuilt the project successfully.

In time, here are my Android Studio details:

Android Studio 3.1.4
Build #AI-173.4907809, built on July 23, 2018
JRE: 1.8.0_152-release-1024-b01 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Mac OS X 10.13.6

EDIT: If prompted to upgrade Gradle, click Upgrade button.

adrianodelvigna commented Sep 19, 2018

@AndroidDeveloperLB, I had the same problem with another project. I followed the instructions from Android Plugin for Gradle release notes; you may try to change your Project Structure settings as (check bold for the changes):

  • Gradle version: 4.4
  • Android Plugin Version: 3.1.0
  • Android Plugin Repository: jcenter, google()
  • Default Library Repository: jcenter

image

I resync'ed Gradle then rebuilt the project successfully.

In time, here are my Android Studio details:

Android Studio 3.1.4
Build #AI-173.4907809, built on July 23, 2018
JRE: 1.8.0_152-release-1024-b01 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Mac OS X 10.13.6

EDIT: If prompted to upgrade Gradle, click Upgrade button.

@AndroidDeveloperLB

This comment has been minimized.

Show comment
Hide comment
@AndroidDeveloperLB

AndroidDeveloperLB Sep 19, 2018

On which sample?
I tried now on "hello-triangle", "image-based-lighting", and "lit-cube" , and all show this error now:

SDK location not found. Define location with sdk.dir in the local.properties file or with an ANDROID_HOME environment variable.

Thing is, it points to a correct place, so it should be fine...

image

AndroidDeveloperLB commented Sep 19, 2018

On which sample?
I tried now on "hello-triangle", "image-based-lighting", and "lit-cube" , and all show this error now:

SDK location not found. Define location with sdk.dir in the local.properties file or with an ANDROID_HOME environment variable.

Thing is, it points to a correct place, so it should be fine...

image

@romainguy

This comment has been minimized.

Show comment
Hide comment
@romainguy

romainguy Sep 19, 2018

Collaborator

@AndroidDeveloperLB You need a local.properties in android/filament-android too.

Collaborator

romainguy commented Sep 19, 2018

@AndroidDeveloperLB You need a local.properties in android/filament-android too.

@AndroidDeveloperLB

This comment has been minimized.

Show comment
Hide comment
@AndroidDeveloperLB

AndroidDeveloperLB Sep 19, 2018

@romainguy It doesn't let me open the project as one with all 3 samples with filament-android , so I can't have it all :

image

Also, I think the samples don't use this, no? Should use the gradle repository instead, no?

I now tried to open each of them separately, and it still doesn't help. Tells me "module not specified", but I can't even choose the module :

image

AndroidDeveloperLB commented Sep 19, 2018

@romainguy It doesn't let me open the project as one with all 3 samples with filament-android , so I can't have it all :

image

Also, I think the samples don't use this, no? Should use the gradle repository instead, no?

I now tried to open each of them separately, and it still doesn't help. Tells me "module not specified", but I can't even choose the module :

image

@romainguy

This comment has been minimized.

Show comment
Hide comment
@romainguy

romainguy Sep 19, 2018

Collaborator

filament-android is a library required by each sample. Just copy your local.properties in filament-android then open a sample.

Collaborator

romainguy commented Sep 19, 2018

filament-android is a library required by each sample. Just copy your local.properties in filament-android then open a sample.

@AndroidDeveloperLB

This comment has been minimized.

Show comment
Hide comment
@AndroidDeveloperLB

AndroidDeveloperLB Sep 19, 2018

@romainguy Copy it? Copy it to where?
As I've shown now, when I open the sample after I've opened the filament-android, it doesn't let me run anything, as it can't find the module to run. Look:

image

AndroidDeveloperLB commented Sep 19, 2018

@romainguy Copy it? Copy it to where?
As I've shown now, when I open the sample after I've opened the filament-android, it doesn't let me run anything, as it can't find the module to run. Look:

image

@romainguy

This comment has been minimized.

Show comment
Hide comment
@romainguy

romainguy Sep 19, 2018

Collaborator

Copy that file inside the filament-android directory.

Collaborator

romainguy commented Sep 19, 2018

Copy that file inside the filament-android directory.

@douglasdcc

This comment has been minimized.

Show comment
Hide comment
@douglasdcc

douglasdcc Sep 21, 2018

@stark25795 your solution was great. Thanks, buddy!

douglasdcc commented Sep 21, 2018

@stark25795 your solution was great. Thanks, buddy!

@Campanari

This comment has been minimized.

Show comment
Hide comment
@Campanari

Campanari Sep 21, 2018

For those who don't need NDK support, uninstall NDK fixes it without the need to upgrade plugin versions.

@edisonw, thanks!

Campanari commented Sep 21, 2018

For those who don't need NDK support, uninstall NDK fixes it without the need to upgrade plugin versions.

@edisonw, thanks!

@cqllzp

This comment has been minimized.

Show comment
Hide comment
@cqllzp

cqllzp Sep 23, 2018

I solved this!miss mips64el-linux-android-4.9 mipsel-linux-android-4.9

cqllzp commented Sep 23, 2018

I solved this!miss mips64el-linux-android-4.9 mipsel-linux-android-4.9

@ktiniatros

This comment has been minimized.

Show comment
Hide comment
@ktiniatros

ktiniatros Sep 24, 2018

Btw you don't really need to find the actual mips64el-linux-android-4.9 mipsel-linux-android-4.9 contents. You can just create a folder with the same name and copy contents from another architecture.

ktiniatros commented Sep 24, 2018

Btw you don't really need to find the actual mips64el-linux-android-4.9 mipsel-linux-android-4.9 contents. You can just create a folder with the same name and copy contents from another architecture.

@SrgGroot

This comment has been minimized.

Show comment
Hide comment
@SrgGroot

SrgGroot Sep 26, 2018

I've been working on getting this solved for a good few days now. I got it working on android after I broke it trying to use an npm package called 'react-native-splash-screen'.

Upgrading my gradle version in the top-level project build gradle to version 3.1.3 solved the problem in my situation. I should mention that before I tried that, I deleted the android folder and rebuilt it because I kept getting some weird errors with 'react-native-firebase' that I had installed and uninstalled earlier.

SrgGroot commented Sep 26, 2018

I've been working on getting this solved for a good few days now. I got it working on android after I broke it trying to use an npm package called 'react-native-splash-screen'.

Upgrading my gradle version in the top-level project build gradle to version 3.1.3 solved the problem in my situation. I should mention that before I tried that, I deleted the android folder and rebuilt it because I kept getting some weird errors with 'react-native-firebase' that I had installed and uninstalled earlier.

@landon-hillyard

This comment has been minimized.

Show comment
Hide comment
@landon-hillyard

landon-hillyard Sep 28, 2018

I have been battling this error for a week now. Could you elaborate on how exactly you upgraded your gradle version. Pretty new in Android Studio so any extra clarity is much appreciated.

landon-hillyard commented Sep 28, 2018

I have been battling this error for a week now. Could you elaborate on how exactly you upgraded your gradle version. Pretty new in Android Studio so any extra clarity is much appreciated.

@SrgGroot

This comment has been minimized.

Show comment
Hide comment
@SrgGroot

SrgGroot Sep 28, 2018

@landon-hillyard I have tried so many things I can't even remember how I got it to work.
Things I've tried:

  • Delete android and node modules folder, run 'npm install' and 'react-native upgrade' to rebuild those folders.
  • Go into 'Project Structure' (top right, folder icon with three blue squares) and then go to 'project' then put in your grade version and android plugin version.
  • Check the top level build.gradle that the version is 3.1.3 like I said in my comment above yours.
  • Check around in your other build.gradle and settings.gradle files to make sure you don't have any version conflicts.

This is a really weird bug and I'm by no means an expert. Took me three days to figure this one out. As I said before I'm working on a React Native project on iOS and Android. The reason why I had to mess with android studio at all was to add the splash screen and app icons. I also had some naming conflicts with 'rn-bridge', however, I want to keep things on topic for this thread.

SrgGroot commented Sep 28, 2018

@landon-hillyard I have tried so many things I can't even remember how I got it to work.
Things I've tried:

  • Delete android and node modules folder, run 'npm install' and 'react-native upgrade' to rebuild those folders.
  • Go into 'Project Structure' (top right, folder icon with three blue squares) and then go to 'project' then put in your grade version and android plugin version.
  • Check the top level build.gradle that the version is 3.1.3 like I said in my comment above yours.
  • Check around in your other build.gradle and settings.gradle files to make sure you don't have any version conflicts.

This is a really weird bug and I'm by no means an expert. Took me three days to figure this one out. As I said before I'm working on a React Native project on iOS and Android. The reason why I had to mess with android studio at all was to add the splash screen and app icons. I also had some naming conflicts with 'rn-bridge', however, I want to keep things on topic for this thread.

@landon-hillyard

This comment has been minimized.

Show comment
Hide comment
@landon-hillyard

landon-hillyard Sep 28, 2018

@SrgGroot Thanks for your suggestions. Attached are the changes I made. No luck. Still have.
"No toolchains found in the NDK toolchains folder for ABI with prefix: mips64el-linux-android"
capture1
image
image
image
image
image

If there are any other suggestions or insights, any help is appreciated.
Should I manually change the version in my build.gradle file?

landon-hillyard commented Sep 28, 2018

@SrgGroot Thanks for your suggestions. Attached are the changes I made. No luck. Still have.
"No toolchains found in the NDK toolchains folder for ABI with prefix: mips64el-linux-android"
capture1
image
image
image
image
image

If there are any other suggestions or insights, any help is appreciated.
Should I manually change the version in my build.gradle file?

@SrgGroot

This comment has been minimized.

Show comment
Hide comment
@SrgGroot

SrgGroot Sep 28, 2018

SrgGroot commented Sep 28, 2018

@landon-hillyard

This comment has been minimized.

Show comment
Hide comment
@landon-hillyard

landon-hillyard Sep 28, 2018

Tried updating the classpath. Got this result.
image
Sorry where are the android and node_modules directories?
image

landon-hillyard commented Sep 28, 2018

Tried updating the classpath. Got this result.
image
Sorry where are the android and node_modules directories?
image

@landon-hillyard

This comment has been minimized.

Show comment
Hide comment
@landon-hillyard

landon-hillyard Sep 28, 2018

I think I figured it out. See below.
image
Uncheck NDK. Then Apply. No longer get the missing NDK toolchains error. Now I am missing a library, but that is a separate issue.

landon-hillyard commented Sep 28, 2018

I think I figured it out. See below.
image
Uncheck NDK. Then Apply. No longer get the missing NDK toolchains error. Now I am missing a library, but that is a separate issue.

@kjknair

This comment has been minimized.

Show comment
Hide comment
@kjknair

kjknair Oct 1, 2018

Update the android tools version in project-level build.gradle.

kjknair commented Oct 1, 2018

Update the android tools version in project-level build.gradle.

@friederbluemle

This comment has been minimized.

Show comment
Hide comment
@friederbluemle

friederbluemle Oct 2, 2018

This is a problem with an old version of the Android Gradle plugin that only surfaced recently due to mips support being removed from the Android SDK. As stated above, it has nothing to do with the filament project.

Solution

Without downloading, updating, or copying anything, you can "fix" the error by simply creating an empty directory where the old version expects it.

Linux

mkdir -p $ANDROID_HOME/ndk-bundle/toolchains/mips64el-linux-android/prebuilt/linux-x86_64

MacOS

mkdir -p $ANDROID_HOME/ndk-bundle/toolchains/mips64el-linux-android/prebuilt/darwin-x86_64

Windows (thanks @dan-r95)

mkdir %ANDROID_HOME%\ndk-bundle\toolchains\mips64el-linux-android\prebuilt\windows-x86_64

The ANDROID_HOME environment variable points to the the root of the Android SDK installation.

friederbluemle commented Oct 2, 2018

This is a problem with an old version of the Android Gradle plugin that only surfaced recently due to mips support being removed from the Android SDK. As stated above, it has nothing to do with the filament project.

Solution

Without downloading, updating, or copying anything, you can "fix" the error by simply creating an empty directory where the old version expects it.

Linux

mkdir -p $ANDROID_HOME/ndk-bundle/toolchains/mips64el-linux-android/prebuilt/linux-x86_64

MacOS

mkdir -p $ANDROID_HOME/ndk-bundle/toolchains/mips64el-linux-android/prebuilt/darwin-x86_64

Windows (thanks @dan-r95)

mkdir %ANDROID_HOME%\ndk-bundle\toolchains\mips64el-linux-android\prebuilt\windows-x86_64

The ANDROID_HOME environment variable points to the the root of the Android SDK installation.

@dan-r95

This comment has been minimized.

Show comment
Hide comment
@dan-r95

dan-r95 Oct 2, 2018

This is a very annoying problem with an old version of the Android Gradle plugin that only surfaced recently due to mips support being removed from the Android SDK. As stated above, it has nothing to do with the filament project.

Without downloading or copying anything, you can "fix" the error by simply creating an empty directory where the older version expects it:

mkdir -p $ANDROID_HOME/ndk-bundle/toolchains/mips64el-linux-android/prebuilt/linux-x86_64

Obviously, $ANDROID_HOME points to the root of the Android SDK installation here. If you are using MacOS, replace linux-x86_64 with darwin-x86_64 in the command above. On Windows use windows-x86_64.

For windows, I had to change the syntax to:
mkdir %ANDROID_HOME%\ndk-bundle\toolchains\mips64el-linux-android\prebuilt\linux-x86_64

dan-r95 commented Oct 2, 2018

This is a very annoying problem with an old version of the Android Gradle plugin that only surfaced recently due to mips support being removed from the Android SDK. As stated above, it has nothing to do with the filament project.

Without downloading or copying anything, you can "fix" the error by simply creating an empty directory where the older version expects it:

mkdir -p $ANDROID_HOME/ndk-bundle/toolchains/mips64el-linux-android/prebuilt/linux-x86_64

Obviously, $ANDROID_HOME points to the root of the Android SDK installation here. If you are using MacOS, replace linux-x86_64 with darwin-x86_64 in the command above. On Windows use windows-x86_64.

For windows, I had to change the syntax to:
mkdir %ANDROID_HOME%\ndk-bundle\toolchains\mips64el-linux-android\prebuilt\linux-x86_64

@fera10

This comment has been minimized.

Show comment
Hide comment
@fera10

fera10 Oct 2, 2018

I am using Windows, and creating the empty folders fixed the problem.
Exactly I created the following directories: \mips64el-linux-android\prebuilt\windows-x86_64
Under my $ANDROID_HOME which in my case is C:\Users\myusername\AppData\Local\Android\sdk\ndk-bundle\toolchains
I run the application again and this time no more errors.
Thanks for the help

fera10 commented Oct 2, 2018

I am using Windows, and creating the empty folders fixed the problem.
Exactly I created the following directories: \mips64el-linux-android\prebuilt\windows-x86_64
Under my $ANDROID_HOME which in my case is C:\Users\myusername\AppData\Local\Android\sdk\ndk-bundle\toolchains
I run the application again and this time no more errors.
Thanks for the help

@CharlesStover

This comment has been minimized.

Show comment
Hide comment
@CharlesStover

CharlesStover Oct 3, 2018

For those of you using stark's solution of downloading an older NDK and merging the two versions, the one you will need is 16c.

CharlesStover commented Oct 3, 2018

For those of you using stark's solution of downloading an older NDK and merging the two versions, the one you will need is 16c.

@skwidz

This comment has been minimized.

Show comment
Hide comment
@skwidz

skwidz Oct 3, 2018

Btw you don't really need to find the actual mips64el-linux-android-4.9 mipsel-linux-android-4.9 contents. You can just create a folder with the same name and copy contents from another architecture.

This worked for me. Thanks @ktiniatros

skwidz commented Oct 3, 2018

Btw you don't really need to find the actual mips64el-linux-android-4.9 mipsel-linux-android-4.9 contents. You can just create a folder with the same name and copy contents from another architecture.

This worked for me. Thanks @ktiniatros

@MNGsulochana

This comment has been minimized.

Show comment
Hide comment
@MNGsulochana

MNGsulochana Oct 4, 2018

Try to update the studio..If u r trying to upload old project then update the gradle as manually to the latest

MNGsulochana commented Oct 4, 2018

Try to update the studio..If u r trying to upload old project then update the gradle as manually to the latest

@yrizk

This comment has been minimized.

Show comment
Hide comment
@yrizk

yrizk Oct 4, 2018

tried what @MNGsulochana said and yeah AS version 3.2 is working

yrizk commented Oct 4, 2018

tried what @MNGsulochana said and yeah AS version 3.2 is working

@petru-sabadac

This comment has been minimized.

Show comment
Hide comment
@petru-sabadac

petru-sabadac Oct 5, 2018

Linux & Mac
cd ~/Library/Android/sdk/ndk-bundle/toolchains
ln -s aarch64-linux-android-4.9 mips64el-linux-android
ln -s arm-linux-androideabi-4.9 mipsel-linux-android

petru-sabadac commented Oct 5, 2018

Linux & Mac
cd ~/Library/Android/sdk/ndk-bundle/toolchains
ln -s aarch64-linux-android-4.9 mips64el-linux-android
ln -s arm-linux-androideabi-4.9 mipsel-linux-android

@Dborah

This comment has been minimized.

Show comment
Hide comment
@Dborah

Dborah Oct 5, 2018

This worked for me. Thanks @petru-sabadac :)

Dborah commented Oct 5, 2018

This worked for me. Thanks @petru-sabadac :)

@angeloraso

This comment has been minimized.

Show comment
Hide comment
@angeloraso

angeloraso Oct 5, 2018

@friederbluemle this works for me. Thanks!

angeloraso commented Oct 5, 2018

@friederbluemle this works for me. Thanks!

@duyhungws

This comment has been minimized.

Show comment
Hide comment
@duyhungws

duyhungws Oct 6, 2018

This worked for me. Thanks @petru-sabadac

duyhungws commented Oct 6, 2018

This worked for me. Thanks @petru-sabadac

@RichieDevereux

This comment has been minimized.

Show comment
Hide comment
@RichieDevereux

RichieDevereux Oct 6, 2018

I had the same problem with a tutorial from Codelabs..

https://codelabs.developers.google.com/codelabs/constraint-layout/index.html?index=..%2F..%2Fio2018#0

When I imported the project to Android Studio 3.14 & 3.2
I got..."No toolchains found in the NDK toolchains folder for ABI with prefix: mips64el

Tried lots of ways and found the easy way.
Just uninstall NDK tools from SDK tools. Uncheck and click ok
Sync project with Gradle files.
It will then bring up update box to update Gradle..update.
Wait to update.
Done.
I actually got this answer from a Chinese site, thankfully Google does great translation.

RichieDevereux commented Oct 6, 2018

I had the same problem with a tutorial from Codelabs..

https://codelabs.developers.google.com/codelabs/constraint-layout/index.html?index=..%2F..%2Fio2018#0

When I imported the project to Android Studio 3.14 & 3.2
I got..."No toolchains found in the NDK toolchains folder for ABI with prefix: mips64el

Tried lots of ways and found the easy way.
Just uninstall NDK tools from SDK tools. Uncheck and click ok
Sync project with Gradle files.
It will then bring up update box to update Gradle..update.
Wait to update.
Done.
I actually got this answer from a Chinese site, thankfully Google does great translation.

@tomalsg

This comment has been minimized.

Show comment
Hide comment
@tomalsg

tomalsg Oct 12, 2018

@petru-sabadac this works for me. Thanks!

tomalsg commented Oct 12, 2018

@petru-sabadac this works for me. Thanks!

@livepk

This comment has been minimized.

Show comment
Hide comment
@livepk

livepk Oct 14, 2018

If you Found error 👍
No toolchains found in the NDK toolchains folder for ABI with prefix: mipsel-linux-android

Then go to gradle-wrapper.properties and change distibutionUrl to letest gradel
i change
distributionUrl=https://services.gradle.org/distributions/gradle-4.6-all.zip
to
distributionUrl=https://services.gradle.org/distributions/gradle-4.9-all.zip

livepk commented Oct 14, 2018

If you Found error 👍
No toolchains found in the NDK toolchains folder for ABI with prefix: mipsel-linux-android

Then go to gradle-wrapper.properties and change distibutionUrl to letest gradel
i change
distributionUrl=https://services.gradle.org/distributions/gradle-4.6-all.zip
to
distributionUrl=https://services.gradle.org/distributions/gradle-4.9-all.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment