-
Notifications
You must be signed in to change notification settings - Fork 13k
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 now requires PIE executables #17437
Comments
this issue should be closed, as there is a commit in that fixes it and says "closes". I'm not sure why it's not. |
except maybe not, because it still happens on latest rust. what gives? |
workaround, since it still seems to be broken: pass |
This is OK to do given: - PIE is supported on Android starting with API 16. - The bots are running API 18. - API < 16 now has a 12.5% market share[0] as of 2015-04-29. Closes rust-lang#17437. [0] https://developer.android.com/about/dashboards/index.html
This is OK to do given: - PIE is supported on Android starting with API 16. - The bots are running API 18. - API < 16 now has a 12.5% market share[0] as of 2015-04-29. Unfortunately, this breaks backtrace support. See rust-lang#17520. Closes rust-lang#17437. [0] https://developer.android.com/about/dashboards/index.html
This is OK to do given: - PIE is supported on Android starting with API 16. - The bots are running API 18. - API < 16 now has a 12.5% market share[0] as of 2015-04-29. Closes rust-lang#17437. [0] https://developer.android.com/about/dashboards/index.html r? @alexcrichton
Can anyone please update https://github.com/rust-lang/rust-wiki-backup/blob/master/Doc-building-for-android.md to reflect this change, as the build with cargo section hack seems not to be necessary anymore |
That's not the actual wiki, but I'll update the wiki |
Except wait. where did the wiki go? |
My point precisely. It's been gone for weeks. |
In that case, nope. :( |
Android's linker no longer supports non-PIE executables: https://android-review.googlesource.com/#/c/93842/
The text was updated successfully, but these errors were encountered: