Package Details: v8-r 8.6.53-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
Licenses: BSD
Conflicts: v8, v8-3.14, v8-3.15, v8-3.20, v8-static-gyp, v8-static-gyp-5.4
Provides: v8
Submitter: JanMarvin
Maintainer: JanMarvin
Last Packager: JanMarvin
Votes: 4
Popularity: 0.21
First Submitted: 2019-09-22 11:01
Last Updated: 2020-07-03 18:29

Required by (2)

Sources (6)

Pinned Comments

JanMarvin commented on 2019-09-22 11:16

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.

Latest Comments

1 2 3 Next › Last »

japhir commented on 2020-06-15 08:58

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

@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

@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

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

tealeaf commented on 2020-06-06 16:34

@HaoZeke: If you edit the PKBGUILD and add these two lines in the build() function it will compile and install there:

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

khughitt commented on 2020-06-06 14:29

In case it helps anyone else, I tracked down the compilation issue I was having to having llvm8 installed instead of llvm (llvm8 is required by some packages in the AUR). Replacing the older version with the current stable release fixes the issue.

JanMarvin commented on 2020-06-06 12:26

@HaoZeke the package builds perfectly fine, but your AUR helper is broken and I have no intention to support its brokenness. You can build this package with Arch's very own makepkg and possibly even other AUR helpers or skip the hassle of building entirely and use the binary package provided in my github repo (https://janmarvin.github.io/archpkgs/).

TL;DR: Attempting to build the package in an unsupported manner will not work and will remain so.

HaoZeke commented on 2020-06-05 22:58

Breaks for me at the moment. The full log is here.

 -> Adding icu missing folders
  -> Building, this will take a while...
ninja: Entering directory `out.gn/Release'
[138/1738] SOLINK ./libv8_libbase.so
FAILED: libv8_libbase.so libv8_libbase.so.TOC
python "../../build/toolchain/gcc_solink_wrapper.py" --readelf="readelf" --nm="nm" --sofile="./libv8_libbase.so" --tocfile="./libv8_libbase.so.TOC" --output="./libv8_libbase.so" -- ../../../../../../../../../usr/bin/clang++ -shared -Wl,-soname="libv8_libbase.so" -Wl,--fatal-warnings -fPIC -Wl,-z,noexecstack -Wl,-z,relro -Wl,-z,defs -Wl,--as-needed -fuse-ld=lld -Wl,--icf=all -Wl,--color-diagnostics -m64 -rdynamic -Wl,-rpath=\$ORIGIN -Wl,-O2 -Wl,--gc-sections -o "./libv8_libbase.so" @"./libv8_libbase.so.rsp"
Traceback (most recent call last):
  File "../../build/toolchain/gcc_solink_wrapper.py", line 153, in <module>
    sys.exit(main())
  File "../../build/toolchain/gcc_solink_wrapper.py", line 136, in main
    result, toc = CollectTOC(args)
  File "../../build/toolchain/gcc_solink_wrapper.py", line 46, in CollectTOC
    result, toc = CollectSONAME(args)
  File "../../build/toolchain/gcc_solink_wrapper.py", line 27, in CollectSONAME
    if 'SONAME' in line:
TypeError: a bytes-like object is required, not 'str'
[147/1738] CXX obj/src/inspector/inspector/Runtime.o
ninja: build stopped: subcommand failed.
==> ERROR: A failure occurred in build().
    Aborting...
Error making: v8-r

JanMarvin commented on 2020-05-19 18:45

@khughitt no clue, works for me, tested just a moment ago with an updated system. You might try this repo but this is the latest release of sunday and requires a patched V8

khughitt commented on 2020-05-19 18:09

Strange -- I'm getting a failure pretty early on in the build:

[41/1654] AR obj/build/config/sanitizers/liboptions_sources.a
FAILED: obj/build/config/sanitizers/liboptions_sources.a 
rm -f obj/build/config/sanitizers/liboptions_sources.a && "../../../../../../../../usr/bin/llvm-ar" -T -r -c -s -D obj/build/config/sanitizers/liboptions_sources.a @"obj/build/config/sanitizers/liboptions_sources.a.rsp"
../../../../../../../../usr/bin/llvm-ar: error while loading shared libraries: libffi.so.6: cannot open shared object file: No such file or directory
[73/1654] CXX obj/torque_base/implementation-visitor.o
[74/1654] CXX obj/torque_base/torque-parser.o
ninja: build stopped: subcommand failed.

System is up to date and libffi 3.3-3 is installed. Tried a clean build with the same result.

Any ideas what could be going on?