is it just me or is the not being build libv8_platform.so?
it seems to be missing.
Search Criteria
Package Details: v8 8.7.220.25-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/v8.git (read-only, click to copy) |
---|---|
Package Base: | v8 |
Description: | Google's open source JavaScript engine |
Upstream URL: | https://v8.dev/ |
Keywords: | compiler interpreter javascript javascript-engine virtual-machine |
Licenses: | BSD |
Conflicts: | v8-3.14, v8-3.14-bin, v8-6.7-static, v8-6.8, v8-r, v8-static-gyp, v8-static-gyp-5.4 |
Submitter: | anatolik |
Maintainer: | None |
Last Packager: | relrel |
Votes: | 15 |
Popularity: | 0.000000 |
First Submitted: | 2015-07-01 16:14 (UTC) |
Last Updated: | 2020-11-26 11:22 (UTC) |
Dependencies (4)
- icu (icu-gitAUR)
- depot-tools-gitAUR (teapot-gclientAUR) (make)
- python2AUR (python2-binAUR) (make)
- rlwrap (optional) – readline support
Required by (1)
- python-pyexecjs (optional)
Sources (2)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 Next › Last »
void.dargon commented on 2016-09-11 21:01 (UTC) (edited on 2016-09-14 05:16 (UTC) by void.dargon)
marcs commented on 2016-09-09 08:40 (UTC)
Latest cherry-pick. Fixed missing libv8.so, Switched to host clang.
marcs commented on 2016-09-06 13:50 (UTC) (edited on 2016-09-06 13:51 (UTC) by marcs)
@dflemstr
Yeah, the docs for GN and V8 are still lacking a bit.
Now I'm using v8-5.2 but I'll have to switch to the latest V8 version very, very soon. So I'll have to work my way through GN. Also testing a build is kinda time consuming I would like to have a 36 cores Xeon beast ;)
dflemstr commented on 2016-09-04 16:15 (UTC)
Hmm... When I build this, it doesn't actually produce a libv8.so file any more, so this line fails:
install -Dm755 out.gn/x64.release/libv8.so $pkgdir/usr/lib/v8/libv8.so
Also, it would be nice to get static libraries being built again but I understand that that's tricky when using GN?
marcs commented on 2016-08-24 11:47 (UTC)
@MagiCarbon try with v8-5.2 has all the libs now.
MagiCarbon commented on 2016-08-24 04:06 (UTC)
sorry, i was wrong. i've asked the author of php-v8js, he said it does support the latest v8. sorry for all confusion.
and the error below occurred because this package lost 'libv8.so', not the v8 version.
configure: error: could not determine libv8 version
marcs commented on 2016-08-23 20:36 (UTC) (edited on 2016-08-23 20:38 (UTC) by marcs)
@r0qs
Gyp is deprecated now for building v8, I switched to GN. So I guess compilation should work next time you try.
@MagiCarbon (and others)
Because seems that some people need v8 5.2 for phpjs (But Why ? http://i.imgur.com/TnQRX6v.gif ;) ) I've added a new package called v8-5.2 which still uses Gyp and it should generate all the libs necessary for phpjs.
r0qs commented on 2016-08-23 15:00 (UTC)
Hi, I'm getting this error during compile:
==> Starting build()...
-> Running gyp...
Updating projects from gyp files...
-> Start building...
ninja: Entering directory `out/Release'
ninja: error: '../../third_party/WebKit/Source/platform/inspector_protocol/DispatcherBase.cpp', needed by 'obj/third_party/WebKit/Source/platform/inspector_protocol/inspector_protocol.DispatcherBase.o', missing and no known rule to make it
==> ERROR: A failure occurred in build().
Aborting...
Anyone knows how to solve?
marcs commented on 2016-08-11 06:41 (UTC) (edited on 2016-08-11 06:41 (UTC) by marcs)
You can simply clone the package and set pkgver=5.2.361.49.
If that version works with php-v8js you should upload a package with the name:
v8-5.2.361.49
Pinned Comments
relrel commented on 2020-10-30 11:56 (UTC) (edited on 2021-02-01 20:07 (UTC) by relrel)
Recommendations
Before installing this package, install
depot-tools-git
and follow its instructions.To speed-up compilation, build on tmpfs and disable tests:
Or using
yay
: