On Wednesday, January 20, 2016 at 7:17:53 PM UTC-5, Thomas Colligan wrote: > > Thanks for your input Jeff. For now it looks like I am just going to have > to target android api 22 and keep an eye out for potential solutions or > changes from the AOSP folks. Will post here if I find anything helpful. > > The annoying thing about this is we will come across the issue and possible solutions sometime in the future. And it will be pure luck while searching for something else. My money is on an Android Studio problem, or a runtime link/loader problem.
Looking over the Android 6.0 security enhancements, I don't see anything that should make a difference; see http://source.android.com/security/enhancements/enhancements60.html. But its hard to tell about side effects from the brief write-ups. Getting back to the build, one thing I am aware that changed was the need for *Position Independent Code*. That changed occurred at Android 5.0; see "*non-PIE linker support removed*" at http://source.android.com/security/enhancements/enhancements50.html). It should not be a problem surfacing now, but you might try with and without -fPIC. Jeff -- -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com. --- You received this message because you are subscribed to the Google Groups "Crypto++ Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
