Package Details: v8 6.9.427.31-1

Git Clone URL: https://aur.archlinux.org/v8.git (read-only)
Package Base: v8
Description: Fast and modern Javascript engine used in Google Chrome.
Upstream URL: https://code.google.com/p/v8/
Keywords: dev engine javascript
Licenses: BSD
Conflicts: v8-3.14, v8-3.15, v8-3.20, v8-static-gyp, v8-static-gyp-5.4
Submitter: anatolik
Maintainer: marcs
Last Packager: marcs
Votes: 11
Popularity: 0.122057
First Submitted: 2015-07-01 16:14
Last Updated: 2018-10-18 09:39

Pinned Comments

marcs commented on 2017-06-21 11:19

Some notes:
* Prefer yaourt instead of pacaur (pacaur works now, but it hides lots of feedback to the user).
* 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 pacaur will save this package in ~/.cache/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).

Build status:
* Working with gcc7.

Latest Comments

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

Tazmain commented on 2018-10-04 13:54

Build fails for me, {standard input}:226988: Error: unknown .loc sub-directive view' {standard input}:226988: Error: junk at end of line, first unrecognized character is-' {standard input}:226990: Error: unknown .loc sub-directive view' {standard input}:226990: Error: unknown pseudo-op:.lvu50714' ninja: build stopped: subcommand failed. ==> ERROR: A failure occurred in build(). Aborting...

dflemstr commented on 2018-09-17 14:29

@marcs did you have time to have a look at this? I haven't seen the new patches being applied yet.

marcs commented on 2018-09-08 17:40

@dflemstr

That's good news, I'll update the package next week.

Thanks

dflemstr commented on 2018-08-31 16:01

Correction: the new version of v8 I proposed does not have the libicu issue.

dflemstr commented on 2018-08-31 15:47

I'd like to see these patches applied: https://gist.github.com/dflemstr/2c06e81da38420d29e702c5bd3601afc

Should fix the build for many users, but the libicu issue might still exist.

thanx commented on 2018-08-30 13:21

Hi Thank you for the package, I am getting following error:

/usr/lib/v8/d8: symbol lookup error: /usr/lib/libv8.so: undefined symbol: _ZN6icu_618ByteSink5FlushEv

It seems like the v8 code has its own icu libraries used during compiling but these are not installed resulting in missing symbols.

Thank you.

ram commented on 2018-07-09 16:35

I'd like to avoid compiling and get this as a pre-compiled package.

thx for the work, guys ;-)

marcs commented on 2018-06-27 16:51

@oneup Thanks for the info, I hope people will find it useful. This package is more of general layout than all-in-one solution due to the complexity of V8.

oneup commented on 2018-06-17 00:02

I'm having a hard time linking against libv8.so. It seems to be due to the fact the libc++.so is located at /usr/lib/v8/libc++.so. I assume that's to not conflict with an existing libc++.so? Unfortunately that makes it difficult both to link against and to dynamically load. Even if you set up pkg-config so that the linker is able to find /usr/lib/v8/libc++.so, you'll still be unable to run the executable because the loader won't know where to find it.

I think adding an RPATH of ${ORIGIN}/v8 to libv8.so would fix the problem, but good luck figuring out how to jam it in to the v8 build process.

For other people running into this issue, you can fix it for your own project by adding -Wl,-rpath,/usr/lib/v8 to your link command. But ideally the libv8.so library itself should know where to find libc++.so without other projects telling the linker/loader where to find it.

marcs commented on 2018-05-28 14:20

@MallardDuck Thanks for the tip, I used your idea. It should build fine now, also package updated to the latest 6.8 version.