That did the trick. Thank you both!
On Fri, Sep 4, 2015 at 2:42 PM, Jakob Kummerow
wrote:
> GYP_DEFINES="v8_use_external_startup_data=0" should do the trick, but I
> haven't tried it.
>
> On Fri, Sep 4, 2015 at 8:37 PM, Charlie Andrews
> wrote:
>
>> ldd /tmp/d8 gives:
>>
>> linux-vdso.so.1 =>
GYP_DEFINES="v8_use_external_startup_data=0" should do the trick, but I
haven't tried it.
On Fri, Sep 4, 2015 at 8:37 PM, Charlie Andrews wrote:
> ldd /tmp/d8 gives:
>
> linux-vdso.so.1 => (0x7ffd7bc52000)
>> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7efedc7a5000)
>> librt.so.1
ldd /tmp/d8 gives:
linux-vdso.so.1 => (0x7ffd7bc52000)
> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7efedc7a5000)
> librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7efedc59d000)
> libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
> (0x7efedc299000)
> libm.so.6 =
You need to copy natives_blob.bin and snapshot_bob.bin along with d8.
(There should probably be a better error message to indicate this.)
On Thu, Sep 3, 2015 at 8:19 PM, Marcin Cieslak wrote:
> On Thu, 3 Sep 2015, 'Charlie Andrews' via v8-users wrote:
>
> > $ mv out/Release/d8 /tmp/d8
> > > $ /
On Thu, 3 Sep 2015, 'Charlie Andrews' via v8-users wrote:
> $ mv out/Release/d8 /tmp/d8
> > $ /tmp/d8
> > Segmentation fault (core dumped)
>
>
> Does anyone know why this happens? Is there a way to build v8 so that I can
> move it around and still have it start properly?
What does your "ldd /tm
Hi all,
I can check out and build v8, and everything works peachy:
$ mkdir /tmp/v8 && cd /tmp/v8
> $ fetch v8 && cd v8
> $ build/gyp_v8 -Dtarget_arch=x64
> $ ninja -C out/Release/ d8
> $ out/out/Release/d8
> V8 version 4.5.103.29 [console: dumb]
> d8>
however, then if I move the binary, I recei
