And another oddity I noticed, is that Boost is not able to detect C++14 being enabled even though I specify -std=c++14 in my jam file. Note the config checks after I run b2:
$ b2 --user-config=clang-android.jam target-os=android toolset=clang-android threadapi=pthread link=static runtime-link=shared threading=multi variant=release --prefix=..\boost_android_arm --builddir=./ --without-python -j1 install Performing configuration checks
- 32-bit : yes - arm : yes - symlinks supported : yes - C++11 mutex : no - lockfree boost::atomic_flag : no - Boost.Config Feature Check: cxx11_auto_declarations : no - Boost.Config Feature Check: cxx11_constexpr : no - Boost.Config Feature Check: cxx11_defaulted_functions : no - Boost.Config Feature Check: cxx11_final : no - Boost.Config Feature Check: cxx11_hdr_mutex : no - Boost.Config Feature Check: cxx11_hdr_tuple : no - Boost.Config Feature Check: cxx11_lambdas : no - Boost.Config Feature Check: cxx11_noexcept : no - Boost.Config Feature Check: cxx11_nullptr : no - Boost.Config Feature Check: cxx11_rvalue_references : no - Boost.Config Feature Check: cxx11_template_aliases : no - Boost.Config Feature Check: cxx11_thread_local : no - Boost.Config Feature Check: cxx11_variadic_templates : no
Seeing that, I would bet money (though not a lot!) on the command line not being what you think it is, and that you're actually building for C++03 John. --- This email has been checked for viruses by AVG. http://www.avg.com