Closed GoogleCodeExporter closed 9 years ago
Looks like GetPointerFromInternalField was removed in V8 version 3.16:
https://groups.google.com/forum/?fromgroups=#!searchin/v8-users/GetPointerFromIn
ternalField/v8-users/aaSY-02HWzA/MP4gRTyB6Z4J
Original comment by cwil...@gmail.com
on 14 Mar 2013 at 2:29
Can you change the subject line to give a better description, ie "Getting error
about GetPointerFromInternalField when compiling"?
Original comment by cwil...@gmail.com
on 14 Mar 2013 at 2:30
I'll change the subject line ... only if I will knew how to do it! :-)
Didn't find some button/option to do that! :-(
Original comment by braila...@gmail.com
on 14 Mar 2013 at 7:56
I was able to get this to build against the newer V8 by switching
GetPointerFromInternalField to GetAlignedPointerFromInternalField. I saw no red
flags with this but I'm unfamiliar with both the v8 and plv8 code bases.
I was also able to run all of my plv8 functions with this switch.
Attached is a patch with the changes if anyone wants it.
Original comment by Nitro...@gmail.com
on 14 Mar 2013 at 4:49
Attachments:
[deleted comment]
you can try "make static" instead of "make"
Original comment by zdenko.v...@gmail.com
on 14 Mar 2013 at 10:45
"make static" gets me this:
../src/store-buffer.h:229:9: error: private field 'heap_' is not used
[-Werror,-Wunused-private-field]
Heap* heap_;
^
1 error generated.
make[3]: ***
[/Users/cwilkes/Documents/workspace/plv8js/build/v8-3.14.5/out/native/obj.target
/v8_base/src/accessors.o] Error 1
make[2]: *** [native] Error 2
make[1]: *** [build/v8-3.14.5/out/native/libv8_snapshot.a] Error 2
make: *** [static] Error 2
which I can probably get around ...
Original comment by cwil...@gmail.com
on 18 Mar 2013 at 1:09
Thanks Nitro ... , I was able to compile dynamic plv8 with your changes from
GetPointerFromInternalField to GetAlignedPointerFromInternalField. Now it
works! Hope that the next stable release of plv8 will include that patch.
Thanks again!
Teo
Original comment by braila...@gmail.com
on 18 Mar 2013 at 7:44
Great. I'm planning to apply the patch for the next release.
Original comment by umi.tan...@gmail.com
on 19 Mar 2013 at 7:37
Applied. The patch broke the oldest supported v8 so I tried keep it for now.
V8's API is terribly changing, so at some point in the future we'll need to
think about the dependency issue. Thanks for the patch anyway.
Original comment by umi.tan...@gmail.com
on 9 Apr 2013 at 7:29
Original comment by umi.tan...@gmail.com
on 9 Apr 2013 at 7:29
Original issue reported on code.google.com by
braila...@gmail.com
on 11 Mar 2013 at 9:08