-
Notifications
You must be signed in to change notification settings - Fork 565
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
Android build failing due to NDK setup problems #5527
Comments
@dolanzhao also hit this on #5515. |
Android support is not in great shape in general: there are private loader problems on Android 9 #3543 and Android 10 #3683. (#5437's loader refactoring proposal may help there.) There is DR-on-Android interest out there and there have been some PR's trying to improve things: maybe we should ask the community to help maintain by getting Android regression tests working. The current tiny set of regular maintainers just do not have the bandwidth to maintain Android and it would simplify things to drop Android support, unless more maintainers step up. |
I was going to mark the Android build as not required for PR merging -- but it's just part of the arm cross-compile job. Maybe we should split it out. |
Fixes the problem of NDK setup failing due to ANDROID_NDK_ROOT pointing to the wrong path. The GitHub VM system preset ANDROID_NDK_ROOT to a location which does not include the necessary resources that the setup process needs. We set the ANDROID_NDK_ROOT to the right location before running the setup script. Fixed: #5527
Mirrors the DynamoRIO/dynamorio#5527 fix by setting ANDROID_NDK_ROOT.
Mirrors the DynamoRIO/dynamorio#5527 fix by setting ANDROID_NDK_ROOT.
This started happening yesterday and has caused every Android build to fail, including the weekly package:
https://github.com/DynamoRIO/dynamorio/actions/runs/2478571712
https://github.com/DynamoRIO/dynamorio/runs/6840580519?check_suite_focus=true
The text was updated successfully, but these errors were encountered: