You can also try building , setting the gn argument
use_custom_libcxx_for_host = true
Argument overview:
Use libc++ instead of stdlibc++ when using the host_cpu toolchain, even if
use_custom_libcxx is false. This is useful for cross-compiles where a custom
toolchain for the target_cpu has been set as the default toolchain, but
use_custom_libcxx should still be true when building for the host.
This issue is because of the libc++ mismatch during the linking process of
clang. I fixed the exact same issue as yours on Linux, with this.
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
---
You received this message because you are subscribed to the Google Groups
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to v8-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/v8-users/951a07df-43a4-4f0f-822c-1ba3d2f1a345%40googlegroups.com.
