1. Compilation and linking succeeds but running the test fails due to missing ___tls_get_addr symbol.
http://www.boost.org/development/tests/develop/developer/CrystaX-NET-apileve...
This is known problem, caused by absence of proper TLS support in clang (x86-only), included to the CrystaX NDK. We're working on this.
2. Linking fails due to missing symbols from iostreams for long double.
http://www.boost.org/development/tests/develop/developer/CrystaX-NET-apileve...
This is known problem too. Again, this is defect of clang, included to the CrystaX NDK, which don't yet fully support long double on 64-bit targets (there was significant change on switch from 32-bit to 64-bit Android in how long double is represented; gcc was adjusted properly, but there are still bugs in supporting that in clang). We're going to fix this too. Both issues are not very critical though - just because a) gcc toolchains don't have such problems, b) x86 is very rare case for Android and c) there is only one Android device on the market, running 64-bit Android - Nexus 9. Of course, we're going to fix this anyway, but this is definitely not the blocker. -- Dmitry Moskalchuk