Arch Linux User Repository

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

FYI: I plan to gradually step away from building v8-r over the next month(s). If you depend on v8-r, please plan ahead — I recommend installing it via the v8-monolith provided by the V8 package, unless someone volunteers to take over maintenance.

For depending packages — sigh — I don’t know. Your best option might be building chromium with the shared libraries flag. (At least this PKGBUILD is maintained by the Arch Linux developers and should build).

For the past five years, I’ve been maintaining the v8-r library for Arch Linux R users: catching breaking changes early, collaborating with Jeroen on fixes in the V8 package, and shipping up-to-date V8 builds.

But things have changed. I never had a personal need for V8 (I only use it for one R package), and building it has become increasingly time-consuming and complex. Google’s focus is on Chrome, and they frequently make changes that break external builds. GCC support has disappeared, and building with system libraries is becoming more difficult.

At first, solving these issues was a fun learning exercise, but it has gradually become a maintenance effort rather than a challenge to solve — and I haven’t been an active Arch Linux user for a few years. My work requires Windows, and privately I’ve been transitioning to macOS.

I plan to ship one or two more builds for V8 (> 7.0.0) once it’s released, but beyond that, I intend to step away from V8 maintenance. I would be happy if someone took over the package — please reach out if you are interested.

Hi, currently you have to remove the lines 133-135. I forgot to check if these are still required and their removal caused a minor headache when figuring out why the Github action build failed. V8 6.0.3 is in CRAN incoming atm, the next v8-r update requires a minor change in V8.

[Edit] V8 6.0.3 is on CRAN and v8-r has been updated as well.

Hello guys, I'm having this issue when trying to install the current version (13.6.70-1):

install: cannot stat 'x64.release/libthird_party_partition_alloc_src_partition_alloc_allocator_shim.so': No such file or directory

Yes, I just tested and that will work for me. The odd thing, though, is the file,v8-primitive.h, has 13 other occurrences of V8_ENABLE_CHECKS where they use #ifdef instead of #if. Still, probably easiest to change the header in my package since it works either way.

Could the same be done for the include diff we added earlier? #define V8_ENABLE_SANDBOX 1?

I think you are right. One of the headers in the package I am maintaining has a #define V8_ENABLE_CHECKS. If I change it to #define V8_ENABLE_CHECKS 1 it fixes the error. Thank you.

Thanks for the report. I am just wondering if V8 expects -DV8_ENABLE_CHECKS=0 and similar for preprocessor flags. They use both if and ifdef for V8_ENABLE_CHECKS, but there’s nothing stopping you from passing -DV8_ENABLE_CHECKS=0 which would be true for #ifdef V8_ENABLE_CHECKS. After all this might be something that the embedder could/should solve and patching wasn’t the right thing to do in the first place?

Hi. I have another error: #if with no expression, this time in the file /usr/include/v8-primitive.h, line 610 & 616. Again, changing the #if to #ifdef fixes the issue. I don't know exactly when this was introduced. The last version I built was 12.7.171.

That should be possible, but depot-tools is a collection of software that is used almost exclusively for Chrome development and probably has no use outside of Google. The AUR packages for depot-tools were often barely maintained (someone put them in the AUR and later probably lost interest because ... nobody really has any use for them). Since the PKGBUILD has been like this for five years, is there a particular reason why you want to see this changed? You need internet access either way to retrieve the package sources, so I don't really see the advantage. You're also welcome to use the binaries for v8-r from Github or my small Arch repository if you don't want to pollute your PATH variable. This also saves about 15 minutes of the computer building the package with all available resources.

Hi, is it possible to use the depot-tools-git package instead of cloning the depot_tools repository?