Package Details: v8 8.0.426.26-1

Git Clone URL: (read-only, click to copy)
Package Base: v8
Description: Fast and modern Javascript engine used in Google Chrome.
Upstream URL:
Keywords: dev engine javascript
Licenses: BSD
Conflicts: v8-3.14, v8-3.14-bin, v8-3.15, v8-3.20, v8-6.7-static, v8-6.8, v8-r, v8-static-gyp, v8-static-gyp-5.4
Submitter: anatolik
Maintainer: marcs
Last Packager: marcs
Votes: 16
Popularity: 0.166814
First Submitted: 2015-07-01 16:14
Last Updated: 2020-03-09 11:37

Pinned Comments

marcs commented on 2017-06-21 11:19

Updates (Oct-2019):

  • Since 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:

  • 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).

Latest Comments

1 2 3 4 5 6 ... Next › Last »

gj545rndmu commented on 2019-09-24 11:14

There is a package that uses a standard linker path now:

Hence, it can be found by other applications such as the R package V8. If you have other packages that rely on v8 at standard linker paths you might want to try the v8-r package as well.

Big thanks to JanMarvin!

izahn commented on 2019-05-31 16:03 by @JanMarvin allowed me to install the R V8 package. It would be great to incorporate the required changes to the main PKGBUILD here.

gj545rndmu commented on 2019-04-15 09:06

@marcs as you can see in other comments below this v8 package here doesn't work with V8 for R. See issue here:

  • /usr/lib/v8 is not a standard linker paths.
  • Even when trying to use your PKGBUILD with standard linker paths: /usr/lib/ undefined symbol: u_strToLower_63

One solution would be to have another package on AUR that we would call v8-R or such. But as JanMarvin pointed out the best solution would be to make it work with this package, right?

What do you think?

marcs commented on 2019-04-10 10:31

hey @dflemstr,

I haven't checked that yaourt was dead, good to know thanks. This package is now compatible with aurman and yay.

I was not aware of the pletora of aur helpers nowadays, I personally don't use them, I just clone a package and build it with makepkg on a specific account designed to do that.

dflemstr commented on 2019-04-08 16:03

I would like to remind about this patch (which might be stale now...):

Building does not work in a lot of cases now when prepare(), build() and check() are run in different phases, which is generally the case in AUR helpers such as yay, pacaur etc.

Note that both yaourt and pacaur are deprecated and yaourt has had a lot of security issues in the past (see for more info) so it might not make sense to recommend using those tools any more.

marcs commented on 2019-03-25 15:53

@znmeb you can limit the number of threads from your makepkg.conf file.

For the rest of the building errors you can change the version using one listed on the V8 branches from:

just change the pkgver variable and you are good to go.

This package is not suited for community IMO, the PKGBUILD is heavily documented to let it know the user that this package needs some configuration (sometimes), the default parameters is what i generally use and it should generally works.

I'm gonna update the PKGBUILD with the missing deps, thanks everyone.

jathroppaPH commented on 2019-03-25 07:58

I am installing this package but it cannot complete the installation.

In file included from ../../src/inspector/
../../src/inspector/v8-debugger-agent-impl.h:124:44: internal compiler error: Segmentation fault
   bool enabled() const { return m_enabled; }
Please submit a full bug report,
with preprocessed source if appropriate.
See  for instructions.
[230/1604] CXX obj/src/inspector/inspector/v8-profiler-agent-impl.o
[231/1604] CXX obj/src/inspector/inspector/v8-inspector-session-impl.o
[232/1604] CXX obj/src/inspector/inspector/value-mirror.o
[233/1604] CXX obj/src/inspector/inspector/v8-runtime-agent-impl.o
[234/1604] ACTION //:run_torque(//build/toolchain/linux:x64)
[235/1604] CXX obj/third_party/googletest/gtest/gtest-matchers.o
[236/1604] CXX obj/third_party/googletest/gtest/gtest-printers.o
[237/1604] CXX obj/third_party/googletest/gtest/gtest.o
[238/1604] SOLINK ./
ninja: build stopped: subcommand failed.
==> ERROR: A failure occurred in build().

I used the PKGBUILD from here:

This is the full installation report in my system:

JanMarvin commented on 2019-03-15 14:39

@zbraniecki you need to install the icudtl.dat file. Can be done adding this line to the PKGBUILD:

install -Dm755 $OUTFLD/icudtl.dat ${pkgdir}/usr/lib/v8/icudtl.dat

zbraniecki commented on 2019-03-11 05:15

I tried to call new Intl.PluralRules(); and it crashed with:

V8 version 7.2.502.25
d8> new Intl.PluralRules

# Fatal error in , line 0
# Failed to create ICU PluralRules, are ICU data files missing?
#FailureMessage Object: 0x7ffeb91884f0
==== C stack trace ===============================

    /usr/lib/ [0x7f66d516c046]
    /usr/lib/ [0x7f66d5142fab]
    /usr/lib/ const*, int, char const*, ...)+0x170) [0x7f66d5163430]
    /usr/lib/ [0x7f66d580e4ee]
    /usr/lib/ [0x7f66d53b0ea2]
    /usr/lib/ [0x7f66d53bfeb8]
    /usr/lib/ [0x7f66d5bcf16b]
Received signal 4 ILL_ILLOPN 7f66d515c5ff
[1]    20807 illegal hardware instruction (core dumped)  d8

I do have libicu installed. Is there a way to link it?

znmeb commented on 2019-03-07 08:45

I'm testing it now - is there any way to limit the number of cores it uses? I have eight cores and it fired off 11 jobs and pushed my workstation so hard it shut down on a thermal overload!

Better yet - get enough votes to move the package into "community"

It's crashing in the tests:

Actual call chain length: 8
setAsyncCallStackDepth(maxDepth): 0
reported: 0
Command: /home/znmeb/Projects/v8/src/v8/ /home/znmeb/Projects/v8/src/v8/test/inspector/protocol-test.js /home/znmeb/Projects/v8/src/v8/test/inspector/debugger/set-async-call-stack-depth.js --random-seed=1823301583 --nohard-abort
exit code: -11
--- CRASHED ---
>>> Too many failures, exiting...
=== inspector/debugger/set-blackbox-patterns ===                          
Tests blackboxing by patterns
Pattern parser error: Uncaught SyntaxError: Invalid regular expression: /(foo([)/: Unterminated character class
Paused in
Paused in
Paused in
Paused in
Paused in
Paused in
Paused in
Command: /home/znmeb/Projects/v8/src/v8/ /home/znmeb/Projects/v8/src/v8/test/inspector/protocol-test.js /home/znmeb/Projects/v8/src/v8/test/inspector/debugger/set-blackbox-patterns.js --random-seed=1823301583 --nohard-abort
exit code: -11
--- CRASHED ---
[04:05|%  67|+ 10255|- 100]: Done                                    
>>> 10355 tests ran
==> ERROR: A failure occurred in check().

I can run it again and post a full logfile if that's necessary.