An app might do something profoundly stupid like uploading contacts in a way you can't easily reverse. Who knows.
-
-
Replying to @CopperheadOS @tedunangst
Rich Felker Retweeted CopperheadOS
Which should be grounds for banning from Play store.https://twitter.com/CopperheadOS/status/775121015504564224 …
Rich Felker added,
1 reply 0 retweets 0 likes -
Replying to @RichFelker @tedunangst
They sometimes get away with breaking compatibility (hidepid=2, stricter SELinux, dropping non-PIE support, etc.).
1 reply 0 retweets 0 likes -
They're very willing to break native code, but the opposite is true for pure Java apps using only documented APIs.
1 reply 0 retweets 0 likes -
Some examples of the outrage they are happy to endure: https://trac.ffmpeg.org/ticket/4928 , https://code.google.com/p/android/issues/detail?id=205565 ….
1 reply 0 retweets 0 likes -
It's because of Android that FFmpeg got rid of ARM text relocations, since they dropped them in 32-bit API level 23.
1 reply 0 retweets 0 likes -
Replying to @CopperheadOS @tedunangst
Hopefully
@musllibc could have gotten them to do it too -- we don't support TEXTRELs anywhere but 32-bit x86.1 reply 0 retweets 0 likes -
FWIW, if Clang + Bionic got static PIE support, they'd likely ban non-PIE static @ all API levels.
2 replies 0 retweets 0 likes -
Replying to @CopperheadOS @tedunangst
All you need to do static PIE is
@musllibc's rcrt1.o and binutils 2.26's --no-dynamic-linker.1 reply 0 retweets 0 likes -
It seems that's not present for http://ld.gold , which is what Android uses on 64-bit ARM.
1 reply 0 retweets 0 likes
Think you could add it? I'm not familiar with gold.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.