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

@JanMarvin: I know that AUR helpers aren't officially supported, but really, it's only adding a couple of lines that I've already provided. Couldn't you do it to make things that little bit easier?

Builds after the gcc10 and binutils update require a patch to build.

@tealeaf sorry, I'm not interested to fix a working PKGBUILD for $aurhelper. If it works with makepkg I'm fine.

@JanMarvin Is there any chance that we could have that minimal update to the current PKGBUILD in the interim, whilst waiting for the pull request to V8 to be merged, so that it builds in yay?

Thanks for all your work on this!

I have prepared a build with python3 as there is only one file left to patch (https://github.com/JanMarvin/v8-R/tree/python3), the test part still requires python2. Once this (https://github.com/jeroen/V8/pull/88) or something similar is merged into the R package V8, I'll likely switch to the python3 branch.

I just reported this over at the yay github page. They told me that this is likely happening due to yay splitting out the prepare() and build() stages of the PKGBUILD, so the environment variables aren't being carried over.

I've edited the PKGBUILD to add:

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

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

at the start of the build() function, and it built successfully for me in yay.

It's because gcc_solink_wrapper.py from https://chromium.googlesource.com/chromium/src/build/ is not yet python 3 ready and yay does not seem to respect the PKGBUILD

Thank you @dickoah and @JanMarvin.

yay -S v8-r failed with

==> Starting build()...
  -> Adding icu missing folders
  -> Building, this will take a while...
ninja: Entering directory `out.gn/Release'
[115/1664] 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 151, in <module>
    sys.exit(main())
  File "../../build/toolchain/gcc_solink_wrapper.py", line 134, in main
    result, toc = CollectTOC(args)
  File "../../build/toolchain/gcc_solink_wrapper.py", line 44, 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'
[132/1664] CXX obj/torque_base/torque-parser.o
ninja: build stopped: subcommand failed.
==> ERROR: A failure occurred in build().
    Aborting...
Error making: v8-r

but

cd /tmp + yay -G v8-r + cd v8-r + makepkg + yay -U v8-r-8.3.129-1-x86_64.pkg.tar.xz

worked fine.

Thanks for the help, but why is that so?

@nevrome You can build it locally, e.g using yay you can something like this

cd /tmp

yay -G v8-r

cd v8-r

makepkg

Hi @nevrome, looks like something fails. I see similar errors when building in a python 3 environment. The warnings are expected and not harmful. Could you elaborate how you try to build?