-
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Patch 1 to build gpgv and unset LD_PRELOAD for Android 5.0.* #2
Conversation
…ot detect that it is running.
Make the process even more foolproof.
Sync with Upstream
I've got the gpgv stuff almost building. Can you tell me more about the |
If an executable is built fully statically, with no dynamic linking at all, then the same binary will work on both PIE systems (android-21 and above), and systems where PIE does not work (older than android-16). refs guardianproject#145 guardianproject#145 closes #2 #2
LD_PRELOAD is pulled from |
If an executable is built fully statically, with no dynamic linking at all, then the same binary will work on both PIE systems (android-21 and above), and systems where PIE does not work (older than android-16). refs guardianproject#145 guardianproject#145 closes #2
If an executable is built fully statically, with no dynamic linking at all, then the same binary will work on both PIE systems (android-21 and above), and systems where PIE does not work (older than android-16). refs guardianproject#145 guardianproject#145 closes #2
Each command calling for the chroot triggers the preloaded libraries from Android's environment. We attempt to unset them. These edits allow building the image and starting the chroot, but lildebi does not detect that it has started at this point. I'm not sure what to do to get that to happen right now.