Arch Linux User Repository

Recommendations

1. Before installing this package, install depot-tools-git and follow its instructions.

2. To speed-up compilation, build on tmpfs and disable tests:

BUILDDIR=/tmp/makepkg makepkg --nocheck

Or using yay:

BUILDDIR=/tmp/makepkg yay -S --mflags --nocheck v8

Build is crashing:

__ running 'download_from_google_storage --no_resume --platform=linux* --no_auth --bucket chromium-clang-format -s v8/buildtools/linux64/clang-format.sha1' in '/d/TMPDIR/yaourt-tmp-znmeb/aur-v8/src' Failed to fetch file gs://chromium-clang-format/5349d1954e17f6ccafb6e6663b0f13cdb2bb33c8 for v8/buildtools/linux64/clang-format. [Err: Traceback (most recent call last): File "/d/TMPDIR/yaourt-tmp-znmeb/aur-v8/src/depot_tools/gsutil.py", line 20, in <module> import urllib2 ModuleNotFoundError: No module named 'urllib2'</module>

@ryanvade I noticed, the problem seems to be with gclient, before the building process, could be related on some ongoing changes on the v8 repository.

Its currently failing to build: Failed to fetch file gs://chromium-clang-format/5349d1954e17f6ccafb6e6663b0f13cdb2bb33c8 for v8/buildtools/linux64/clang-format. [Err: [E2018-01-02T22:20:08.898896-06:00 1169 0 annotate.go:242] original error: package "infra/python/wheels/cffi/linux-amd64_cp32_abi3" is not registered

==> Building and installing package
==> Making package: v8 6.4.388.6-1 (Wed 13 Dec 16:17:42 CET 2017)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Cloning depot_tools git repo...
Cloning into bare repository '/tmp/yaourt-tmp-blablabla/aur-v8/depot_tools'...
remote: Sending approximately 29.67 MiB ...
remote: Counting objects: 25739, done
remote: Finding sources: 100% (25739/25739)
remote: Total 50586 (delta 20798), reused 50586 (delta 20798)
Receiving objects: 100% (50586/50586), 44.23 MiB | 3.47 MiB/s, done.
Resolving deltas: 100% (20798/20798), done.
  -> Found v8.pc
  -> Found v8_libbase.pc
  -> Found v8_libplatform.pc
  -> Found d8
  -> Found ctest.patch
==> Validating source files with sha256sums...
    depot_tools ... Skipped
    v8.pc ... Passed
    v8_libbase.pc ... Passed
    v8_libplatform.pc ... Passed
    d8 ... Passed
    ctest.patch ... Passed
==> Extracting sources...
  -> Creating working copy of depot_tools git repo...
Cloning into 'depot_tools'...
done.
==> Starting prepare()...
  -> Creating Python Virtual Environment
Traceback (most recent call last):
  File "/usr/bin/virtualenv2", line 6, in <module>
    from pkg_resources import load_entry_point
ImportError: No module named pkg_resources

EDIT: solved! i needed to install python-pkgconfig and/or python-pip manually

It still does not install the headers for libplatform! For that add: install -d ${pkgdir}/usr/include/libplatform install -Dm644 include/libplatform/*.h ${pkgdir}/usr/include/libplatform

@chendaniely > would it make sense to have this depend/work on the gcc6 aur package? I'd rather not, this package is already on the heavy side, and gcc is time/resource consuming to compile from aur. Keep a downgrade of gcc if possible, get gcc6.3.1 from here: https://archive.archlinux.org/ > sjewo has made a PKGBUILD patch to work with gcc6 that might help. > It's based on v8-314, but could be a reference. The problem is a compiling error with gcc7 not a segfault with gcc6 so it is unrelated.

would it make sense to have this depend/work on the gcc6 aur package? edit: sjewo has made a PKGBUILD patch to work with gcc6 that might help. It's based on v8-314, but could be a reference. https://github.com/jeroen/V8/issues/32

Updates (Oct-2019):

• Since 7.7.299.10-1 v8 uses standard lib paths as requested (apart what is needed to run d8).

• For specific uses like R, I strongly recommend the package v8-r which has a custom configuration for R.

Some notes:

• Latest version is based on the version on branch-heads from the V8 repositories, I stick to stable, but sometimes I could use beta but I never use dev (check this: https://omahaproxy.appspot.com/).

• This is a "generic" configuration, v8 is highly configurable, if you need v8 for some specific integration please check the Google documentation.

• Prefer yay/aurman instead of yaourt/pacaur.

• Gclient has to download the whole V8 repo, it takes some time to complete (depending on your internet connection).

• This package requires around 3/4 gigs of space so be sure to have a large enough /tmp partition if you use yaourt, also be aware that aurman/yay/pacaur will save this package in ~/.cache/(aurman|yay|pacaur)/v8, so be sure to have a /home partition with enough space.

• The build and testing process takes some time, I recommend to use at least a 4 cores with 8 threads cpu, better an 8 cores 16 threads cpu.

• If you have at least 32GB of RAM you can use a ram partition to speed up the build process (yaourt uses /tmp by default).