I downloaded the old NDK r8e and was able to reproduce the problem. It is obviously a bug in the NDK.
Strangely enough we refer in the user’s guide to r8e as a verified version, which means that we have tested this version in the past and that it worked fluently then. Without digging depth into further analysis it is not possible to tell you what exactly is causing the problem now. It might be a mixture of newer SDK platform tools with an old NDK.
Due to the fact that the r8e version is outdated now, we will not further analyse the problem but will update the documentation.
Please download and use NDK r9d:
64bit: https://dl.google.com/android/ndk/androi...x86_64.zip
32bit: http://dl.google.com/android/ndk/android...ws-x86.zip
We are working on the support for NDK r10.
Support for NDK r10c is included in the latest release 1.00.5225.
Please use the latest build and NDK r10c from https://developer.android.com/tools/sdk/ndk/index.html
Strangely enough we refer in the user’s guide to r8e as a verified version, which means that we have tested this version in the past and that it worked fluently then. Without digging depth into further analysis it is not possible to tell you what exactly is causing the problem now. It might be a mixture of newer SDK platform tools with an old NDK.
Due to the fact that the r8e version is outdated now, we will not further analyse the problem but will update the documentation.
Please download and use NDK r9d:
64bit: https://dl.google.com/android/ndk/androi...x86_64.zip
32bit: http://dl.google.com/android/ndk/android...ws-x86.zip
We are working on the support for NDK r10.
Support for NDK r10c is included in the latest release 1.00.5225.
Please use the latest build and NDK r10c from https://developer.android.com/tools/sdk/ndk/index.html