Package Details: v8-r 13.7.119-1

Git Clone URL: https://aur.archlinux.org/v8-r.git (read-only, click to copy)
Package Base: v8-r
Description: Google's open source JavaScript and WebAssembly engine
Upstream URL: https://v8.dev
Keywords: d8 javascript v8
Licenses: BSD
Conflicts: v8, v8-3.14, v8-6.7-static, v8-static-gyp, v8-static-gyp-5.4, v8.3.14-bin
Provides: v8
Submitter: JanMarvin
Maintainer: JanMarvin
Last Packager: JanMarvin
Votes: 10
Popularity: 0.030617
First Submitted: 2019-09-22 11:01 (UTC)
Last Updated: 2025-04-19 04:02 (UTC)

Pinned Comments

JanMarvin commented on 2019-09-22 11:16 (UTC) (edited on 2021-09-24 14:34 (UTC) by JanMarvin)

This package is required for the R-package V8 (https://github.com/jeroen/V8). It is frequently updated, though unless it is broken, users must not build all updates. Since V8 contains a large codebase and compilation takes a while, I recommend to build it in a directory and not with an AUR-helper.

[Edit:] For binary builds please see: https://garbuszus.de/archpkgs

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

JanMarvin commented on 2020-10-20 13:09 (UTC)

@levitsky please read the manual (https://github.com/jeroen/v8). To use the V8 package in R you need to have this package installed and afterwards build the V8 package in R.

levitsky commented on 2020-10-20 12:49 (UTC)

I'm having trouble getting it to work. I have built and installed the package but it doesn't install anything into /usr/lib/R? So doing library(V8) from R fails. However, this package conflicts with v8 package, so I can't have both. What am I missing?

leonardof commented on 2020-08-22 15:15 (UTC)

Exactly, I was running out of memory! Haven't bothered with swap in many years now, but it seems 8 GB RAM are modest by today's standards.

Thanks for the repo. At first, I wasn't able to compile the V8 package with it, but I noticed the glibc version in the error message, enabled [testing], and everything worked.

JanMarvin commented on 2020-08-22 12:53 (UTC)

@leonardof did you somehow run out of memory? That's my best guess from your output (you get english locales running export LANG=C). You could install the binary from my arch repo on github.

leonardof commented on 2020-08-22 12:26 (UTC)

Compilation fails for me despite binutils 2.34-5; not using any AUR helper. The output of build() will be on pastebin for a month.

JanMarvin commented on 2020-08-22 10:54 (UTC)

Be aware that currently building fails with an ld segfault. I assume that this is related to a binutils 2.35-1 update (see my bug report: https://bugs.archlinux.org/task/67671?project=1&string=binutils)

japhir commented on 2020-06-15 08:58 (UTC)

I did install the package with my AUR helper, yay, and simply added this line to my /etc/pacman.conf: IgnorePkg = v8-r I can comment this line when I want to update the package.

Just thought I'd share, might be useful for others!

tealeaf commented on 2020-06-07 11:30 (UTC)

@JanMarvin: Thank you! Much appreciated.

(I haven't checked, but I suspect that the 

export CC=/usr/bin/clang
export CXX=/usr/bin/clang++

exports might also want to be in build() build as well to avoid potential problems in the same situation.)

JanMarvin commented on 2020-06-07 11:21 (UTC)

@tealaf Thanks for the report. A valid claim and I'll add the required lines for next weeks build.

tealeaf commented on 2020-06-06 16:42 (UTC)

@JanMarvin: Can I mention that this PKGBUILD fails under makepkg if you use the --noextract option, which runs build() but not prepare(). According to the makepkg man page:

This is handy if you want to go into $srcdir/ and manually patch or tweak code, then make a package out of the result.

As this is a supported, documented use of makepkg that fails with the current PKGBUILD, would you consider adding the two exports to build() as a legitimate bugfix?

For reference, the two exports required are:

export PATH=${srcdir}/bin:`pwd`/depot_tools:"$PATH"
export GYP_GENERATORS=ninja

in the build() function.

Thanks for considering.

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »