It looks like it's a git repo, I would guess you be able to just check out 
the tools that were available at the same time as the version of V8 that 
you want to build?

--Zac

On Wednesday, September 6, 2017 at 10:27:12 PM UTC-7, Chris Hillery wrote:
>
> I've seen several earlier threads on variants of this problem, but none of 
> the solutions appear to work any more as they were for older versions of 
> v8, or because depot_tools has moved on, or both.
>
> I need to build v8 5.9 for Centos 6. The big problem is that Centos 6 uses 
> glibc 2.12, which is quite ancient, and all of the tools that are 
> downloaded by the v8 build process are built using newer versions of glibc. 
> This includes gn and clang in particular, but also the binutils tools. 
> About the only thing that does work as expected is gclient.
>
> The closest I've gotten so far is attempting to use the older gyp method, 
> which at least bypasses gn. I believe I could also build gn for Centos 6, 
> although it's challenging.
>
> I can also request it not to use the built-in clang - the Centos 6 image I 
> am using does have gcc 4.8.2 installed which should be good enough. However 
> when not using clang, it is also necessary to skip the built-in sysroot. 
> When I do that, I get errors about glib-2.0, gmodule-2.0, and other 
> packages I don't recognize not being available.
>
> Basically I'm wondering if there are any ways forward, in particular if 
> anyone has successfully traveled this road already. Is v8 no longer 
> officially supported for Centos / Red Hat 6? Are there any ways to get the 
> older versions of the tools from days when v8 was built for Centos 6? (I 
> assume those days existed at some point...)
>
> Thanks,
> Ceej
> aka Chris Hillery
>

-- 
-- 
v8-users mailing list
[email protected]
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to