What is the minimum version of gcc required to build v8 8.3, which appears to be the most recent stable version of v8?
--
--
v8-users mailing list
v8-u...@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+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/v8-users/509ffff7-27c9-49fe-b98b-1aa4761d10deo%40googlegroups.com.
Probably 5.x.There is a recent commit that mentions "GCC versions older than 6 are still used by the CQ bots".We definitely don't support GCC 4.x any more.Most of our buildbots use Ubuntu Xenial (16.04 LTS) currently, so whatever GCC version is in there should definitely work -- looks like that would be 5.3.1 if I'm reading https://packages.ubuntu.com/xenial/gcc right.
On Tue, Jun 30, 2020 at 4:22 AM Nupoor Kotasthane <nupoo...@gmail.com> wrote:
What is the minimum version of gcc required to build v8 8.3, which appears to be the most recent stable version of v8?--
--
v8-users mailing list
v8-u...@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-u...@googlegroups.com.
Perhaps this might help.
is_clang = false
use_custom_libcxx_for_host = true
---Argument description----
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.
I was able to build latest V8 on CentOS 8