Building V8 Libraries Help. (Repositories Offline?)

[Allen Ng]

Hello all, 

I do not know if this is the right place for this but it can't hurt to try! I am currently trying to build V8 Libraries following this tutorial, Building V8 Libraries Tutorial. I am trying to build these on a s390x Ubuntu Docker Container on a SLES 12  instance on the LinuxONE Community Cloud. I have been following along with it but when it comes time to do "make dependencies" I get an error that sasy teh SVN can not connect to the gyp.googlecode.com/svn/trunks repository. I looked around on Google and it seems that repository has been taken offline. There are two other repositories down the line, googletest and googlemock repositories, that also seem to have been taken down and merged into one single repository. 

So I was wondering if any of you know of a different tutorial that would help me here. I have found github mirrors of gyp.googlecode.com/svn/trunk and it seems to work but when I run the next command of  "make s390x -j4 library=shared" i get an error after replacing the googletest and googlemock repositories with the new combined repository managed by Google. The error is a "No rule to make target for gtest_main.o. 

The main thing I am looking for is if there are any up to date tutorials on building the V8 Libraries on a LinuxONE Community Cloud Instance. If you need anymore information please feel free to ask.

Thanks,

Allen

[Jochen Eisinger]

Please reach out to IBM team. The svn server referenced in that documentation doesn't exist anymore, however, the s390(x) port is meanwhile (completely?) upstream, so just following the regular v8 build instructions might work?

--
--
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.
For more options, visit https://groups.google.com/d/optout.

[Ben Noordhuis]

What V8 version are you trying to build? To the best of my knowledge,
V8 5.1 and up should build out of the box on s390x if you follow the
steps described here[0].

[0] https://github.com/v8/v8/wiki -> Usage -> Building from source

[Ben Noordhuis]

On Wed, Jul 20, 2016 at 8:59 AM, Jochen Eisinger <joc...@chromium.org> wrote:
> Please reach out to IBM team. The svn server referenced in that
> documentation doesn't exist anymore, however, the s390(x) port is meanwhile
> (completely?) upstream, so just following the regular v8 build instructions
> might work?

I've passed it on to my coworkers at IBM.

[Joran Siu]

Hi Allen,

I'm with the IBM team supporting the S390 port of V8.  Which version of V8 did you want to build?   

The building V8 libraries tutorial you mentioned was updated yesterday with the newer locations of make dependencies.   However, they are for building older levels of V8 (3.14 / 3.28).  As mentioned by Ben, there is a full S390 port in V8 5.1 or later.   I'll work with the LoZ ecosystems team to get the newer levels of V8 updated on that instruction pages.

FWIW, since it looked like you were building 3.28, we did work out the corresponding levels of the gmock / gtest / gyp dependencies to the levels that were pulled from the original SVN repositories  You should be able to just run these commands from the extracted v8z directory (after make 'dependencies') and continue on:

# For 3.28, with the SVN repositories gone for gmock, gtest and gyp, use the following
# to git clone and download the matching revisions.
git clone https://chromium.googlesource.com/external/gyp  build/gyp
cd build/gyp
git reset --hard a3e2a5caf24a1e0a45401e09ad131210bf16b852
cd ../..
git clone https://chromium.googlesource.com/external/gmock testing/gmock
cd testing/gmock
git reset --hard 896ba0e03f520fb9b6ed582bde2bd00847e3c3f2
cd ../..
git clone https://chromium.googlesource.com/external/gtest testing/gtest
cd testing/gtest
git reset --hard 4650552ff637bb44ecf7784060091cbed3252211
cd ../..

I'll make the changes to our existing repos to use these new repositories instead, so you won't have to go through manual patching.  Will update this thread once that's completed.

Sorry about the extra churn!

Thanks,

-Joran

[Allen Ng]

Hello All,

Awesome, that is great news! Thank you guys for the quick answers, I really appreciate it! 

Thanks for the help,

Allen

On Tuesday, July 19, 2016 at 6:33:07 PM UTC-4, Allen Ng wrote: