Package Details: v8 6.0.286.57-1

Git Clone URL: https://aur.archlinux.org/v8.git (read-only)
Package Base: v8
Description: Fast and modern Javascript engine used in Google Chrome.
Upstream URL: https://code.google.com/p/v8/
Keywords: dev engine javascript
Licenses: BSD
Conflicts: v8-3.14, v8-3.15, v8-3.20, v8-static-gyp, v8-static-gyp-5.4
Submitter: anatolik
Maintainer: marcs
Last Packager: marcs
Votes: 9
Popularity: 0.004634
First Submitted: 2015-07-01 16:14
Last Updated: 2017-08-30 14:36

Pinned Comments

marcs commented on 2017-06-21 11:19

Some notes:
* Prefer yaourt instead of pacaur (pacaur works now, but it hides lots of feedback to the user).
* 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 pacaur will save this package in ~/.cache/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).

Build status:
* Working with gcc7.

Latest Comments

marcs commented on 2017-07-22 13:21

@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.

chendaniely commented on 2017-07-20 22:16

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

marcs commented on 2017-06-21 11:19

Some notes:
* Prefer yaourt instead of pacaur (pacaur works now, but it hides lots of feedback to the user).
* 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 pacaur will save this package in ~/.cache/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).

Build status:
* Working with gcc7.

marcs commented on 2017-06-21 11:05

@OdinEidolon gclient has to download the whole repository takes quite some time depending on your internet connection.

@chendaniely I really don't like pacaur, it doesn't display msg2 lines (in prepare) that in this package are important because some steps take long time to complete.

You get that error because of pacaur, It's an easy fix but as I checked now the build is broken because of gcc7.

chendaniely commented on 2017-06-14 14:30

@OdinEidolon
for me it seems like it (`Running: gclient sync --with_branch_heads `) hangs, but it just takes a (long) while for it go get past that step

chendaniely commented on 2017-06-14 14:16

I'm getting a syntax error in the python script:

$ pacaur -S v8
:: Package v8 not found in repositories, trying AUR...
:: resolving dependencies...
:: looking for inter-conflicts...

AUR Packages (1) v8-5.9.211.27-1

:: Proceed with installation? [Y/n]

:: Retrieving package(s)...
:: v8 build files are up-to-date -- skipping
[sudo] password for dchen:
:: Checking v8 integrity...
==> Making package: v8 5.9.211.27-1 (Wed Jun 14 10:10:19 EDT 2017)
==> Retrieving sources...
-> Updating depot_tools git repo...
Fetching origin
-> Found v8.pc
-> Found v8_libbase.pc
-> Found v8_libplatform.pc
-> Found d8
-> Found icu59.diff
==> Validating source files with sha256sums...
depot_tools ... Skipped
v8.pc ... Passed
v8_libbase.pc ... Passed
v8_libplatform.pc ... Passed
d8 ... Passed
icu59.diff ... Passed
:: Building v8 package(s)...
==> Making package: v8 5.9.211.27-1 (Wed Jun 14 10:10:27 EDT 2017)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Removing existing $pkgdir/ directory...
==> Starting build()...
-> Running GN...
Traceback (most recent call last):
File "../depot_tools/gn.py", line 15, in <module>
import gclient_utils
File "/home/dchen/.cache/pacaur/v8/src/depot_tools/gclient_utils.py", line 266
except OSError, e:
^
SyntaxError: invalid syntax
==> ERROR: A failure occurred in build().
Aborting...
:: failed to build v8 package(s)

OdinEidolon commented on 2017-06-13 08:23

Installation seems to get stuck at:

Running: gclient sync --with_branch_heads

marcs commented on 2017-05-19 08:03

@kageurufu v8-3.14 has conflicts with v8

v8-3.14-bin can be installed side-by-side, went overboard with package conflicts.

kageurufu commented on 2017-05-17 17:47

Why does this conflict with v8-3.14/-bin?

v8-3.14-bin installs /usr/lib/libv8.so.3.14.5 specifically so it can be installed side-by-side with 5.x+

marcs commented on 2017-05-10 11:23

Testing the 5.9 update:
* introduced minimal patch for icu 59
* one assert failing related to internationalization: https://groups.google.com/forum/#!topic/v8-users/tkN1B9RvnLc

All comments