Obsolete
Status Update
Comments
en...@google.com <en...@google.com>
pa...@gmail.com <pa...@gmail.com> #2
Note that the bug surfaced when I tried our app on android 5
ha...@guardianproject.info <ha...@guardianproject.info> #3
I'm also seeing this problem with our library IOCipher (https://github.com/guardianproject/IOCipher ). It all builds and works fine, until I switch the test suite from targeting android-15 to android-21, then running the tests on a android-19 (4.4.4) ROM. The NDK build uses r10d, and the IOCipher NDK build targeting android-7.
I found this workaround, which seems to work:
LOCAL_LDFLAGS += -fuse-ld=bfd
I found this workaround, which seems to work:
LOCAL_LDFLAGS += -fuse-ld=bfd
en...@google.com <en...@google.com> #4
please reopen if you still see this with r12.
Description
In short, gold linker (which is used by default) produces corrupt binaries that do not load. If I set -fuse=bfd then binaries are OK and load properly.
the error that I get at load time:
E/dalvikvm( 3993): dlopen("/data/app-lib/
W/System.err( 3993): java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "__exidx_end" referenced by "libXYZ.so"...
Note, that I also use -Wl,--no-undefined which means that the linking was supposed to fail. There is old bug report that was never addressed (it has sample project there):