Unfortunately, the issues with x86 will not result in a failure to link. Instead, your shared object file will be mysteriously unable to load at runtime due to missing symbols (assuming you're using the library for anything nontrivial; the simplest of examples will work fine).
However, you're treading into extremely dangerous territory by linking against both libc++ and libstdc++. While you may have gotten things to compile, you're almost guaranteed to run into nightmarish bugs at runtime which simply do not make sense.
Why do you need to link against libc++ at all? Simply setting APP_STL to be gnustl_static should make everything work fine.
Thanks for the catch on -llog. We also likely will require -lm as well.
roschuma
However, you're treading into extremely dangerous territory by linking against both libc++ and libstdc++. While you may have gotten things to compile, you're almost guaranteed to run into nightmarish bugs at runtime which simply do not make sense.
Why do you need to link against libc++ at all? Simply setting APP_STL to be gnustl_static should make everything work fine.
Thanks for the catch on -llog. We also likely will require -lm as well.
roschuma