Update

-DANDROID_ALLOW_UNDEFINED_SYMBOLS was set to TRUE in my Hello World app's build.gradle which suppress many link errors. After setting it FALSE, I'm getting lots link errors:

/home/ping/.torq_cache/v8/v8-5.8.283.38/android-release-all/x86_64/libv8_base.a(api.o):../../src/api.cc:function v8::debug::Script::GetPossibleBreakpoints(v8::debug::Location const&, v8::debug::Location const&, std::vector<v8::debug::Location, std::allocator<v8::debug::Location> >*) const: error: undefined reference to 'std::_Rb_tree_increment(std::_Rb_tree_node_base const*)'
/home/ping/.torq_cache/v8/v8-5.8.283.38/android-release-all/x86_64/libv8_base.a(api.o):../../src/api.cc:function v8::debug::Coverage::ScriptData::GetFunctionData(unsigned long): error: undefined reference to 'std::__throw_out_of_range(char const*)'
/home/ping/.torq_cache/v8/v8-5.8.283.38/android-release-all/x86_64/libv8_base.a(api.o):../../src/api.cc:function v8::debug::Coverage::GetScriptData(unsigned long): error: undefined reference to 'std::__throw_out_of_range(char const*)'
/home/ping/.torq_cache/v8/v8-5.8.283.38/android-release-all/x86_64/libv8_base.a(assembler.o):../../src/assembler.cc:function v8::internal::operator<<(std::ostream&, v8::internal::ExternalReference): error: undefined reference to 'std::ostream& std::ostream::_M_insert<void const*>(void const*)'
/home/ping/.torq_cache/v8/v8-5.8.283.38/android-release-all/x86_64/libv8_base.a(assembler.o):../../src/assembler.cc:function v8::internal::operator<<(std::ostream&, v8::internal::ExternalReference): error: undefined reference to 'std::basic_ostream<char, std::char_traits<char> >& std::__ostream_insert<char, std::char_traits<char> >(std::basic_ostream<char, std::char_traits<char> >&, char const*, long)'
/home/ping/.torq_cache/v8/v8-5.8.283.38/android-release-all/x86_64/libv8_base.a(assembler.o):../../src/assembler.cc:function v8::internal::operator<<(std::ostream&, v8::internal::ExternalReference): error: undefined reference to 'std::basic_ostream<char, std::char_traits<char> >& std::__ostream_insert<char, std::char_traits<char> >(std::basic_ostream<char, std::char_traits<char> >&, char const*, long)'
/home/ping/.torq_cache/v8/v8-5.8.283.38/android-release-all/x86_64/libv8_base.
a(assembler.o):../../src/assembler.cc:function v8::internal::operator<<(std::ostream&, v8::internal::ExternalReference): error: undefined reference to 'std::basic_ios<char, std::char_traits<char> >::clear(std::_Ios_Iostate)'
/home/ping/.torq_cache/v8/v8-5.8.283.38/android-release-all/x86_64/libv8_base.a(assembler.o):../../src/assembler.cc:function v8::internal::operator<<(std::ostream&, v8::internal::ExternalReference): error: undefined reference to 'std::basic_ostream<char, std::char_traits<char> >& std::__ostream_insert<char, std::char_traits<char> >(std::basic_ostream<char, std::char_traits<char> >&, char const*, long)'
...

Here is the list of v8 libraries linked with:
-rw-rw-r-- 1 ping ping  5914876 Jun 30 09:10 libicui18n.a
-rw-rw-r-- 1 ping ping  3263978 Jun 30 09:10 libicuuc.a
-rw-rw-r-- 1 ping ping 33332546 Jun 30 09:10 libv8_base.a
-rw-rw-r-- 1 ping ping   198362 Jun 30 09:03 libv8_libbase.a
-rw-rw-r-- 1 ping ping   114224 Jun 30 09:07 libv8_libplatform.a
-rw-rw-r-- 1 ping ping    16638 Jun 30 09:03 libv8_libsampler.a
-rw-rw-r-- 1 ping ping   215354 Jun 30 09:10 libv8_nosnapshot.a

Quick note that this bug was brought up by Adobe during a meeting as one that was blocking some of their work. 

+hablich@ for V8

I think Peter was the last person who did try to embed V8 on Android. Peter, any clue what's going on?

The build configuration in #1 is a bit unusual - you have target_cpu = x64 and v8_target_cpu = arm64, so the C++ code is being compiled for x64, but the v8 jit is generating arm64 code and running it in V8's arm64 simulator. This is the way we would usually setup a simulator build on a host machine in order to test v8's arm64 codegen on an x64 host desktop machine, however if you are wanting to run in an x64 Android simulator you shouldn't need this. 

Can with cleaning the out directory then configuring gn to just have target_cpu = "x64" and drop the "v8_target_cpu"?

I didn't try this on Android unfortunately - I wonder if Henry had any luck yet?

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot