[v8-users] Re: undefined reference to symbol pthread_condattr_setclock
I use Eclipse and found no easy way to specify the linker options. After all it works now. Am Sonntag, 29. März 2015 14:52:20 UTC+2 schrieb roiber: > > I compiled v8 on ubuntu 14.10 x64 with gcc. When i try to embed it in my > application the linker says pthread_condattr_setclock is missing. This > seems to be an optional feature of the POSIX pthread implementation. Could > it be that it is missing in glibc? > > getconf GNU_LIBPTHREAD_VERSION > gives > NPTL 2.19 > > -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[v8-users] V8 build problem -- Unterminated quoted string ?
Linux x86 3.13.0-48-generic #80-Ubuntu SMP Thu Mar 12 11:16:18 UTC 2015 i686 i686 i686 GNU/Linux gclient.py 0.7 ~$ cd /usr/local/src/v8 $ make native make[1]: Entering directory `/usr/local/src/v8/out' CXX(target) /usr/local/src/v8/out/native/obj.target/v8_base/src/accessors.o /usr/local/src/v8/third_party/llvm-build/Release+Asserts/bin/clang++: 2: /usr/local/src/v8/third_party/llvm-build/Release+Asserts/bin/clang++: Syntax error: Unterminated quoted string make[1]: *** [/usr/local/src/v8/out/native/obj.target/v8_base/src/accessors.o] Error 2 make[1]: Leaving directory `/usr/local/src/v8/out' make: *** [native] Error 2 -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [v8-users] clang vs gcc
On Sun, Mar 29, 2015 at 2:46 PM, roiber wrote: > Hello, > > the default compiler for v8 is clang. Does that mean that i have to compile > my project where i embed v8 in also has to be compiled with clang? > > thanks > roiber Embedders don't have to build with clang. You will need at least g++ 4.8 or VS 2013 though. -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[v8-users] Re: undefined reference to symbol pthread_condattr_setclock
ok, it seems to be the order of the -l arguments to the linker. But now i get many defined references from v8 libraries. what is the required link oder for these? Am Sonntag, 29. März 2015 14:52:20 UTC+2 schrieb roiber: > > I compiled v8 on ubuntu 14.10 x64 with gcc. When i try to embed it in my > application the linker says pthread_condattr_setclock is missing. This > seems to be an optional feature of the POSIX pthread implementation. Could > it be that it is missing in glibc? > > getconf GNU_LIBPTHREAD_VERSION > gives > NPTL 2.19 > > -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[v8-users] libplatform library not included ?
Hi Together, Sorry for my beginner question but gets the libplatform binary not atached to the libv8.so when i compile the whole thing from scratch (with components=shared_library) ? So if not which .o whiles do i need to give to g++ as parameters to compile my own code ? Thanks in advance ! Cheers, Max -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[v8-users] undefined reference to symbol pthread_condattr_setclock
I compiled v8 on ubuntu 14.10 x64 with gcc. When i try to embed it in my application the linker says pthread_condattr_setclock is missing. This seems to be an optional feature of the POSIX pthread implementation. Could it be that it is missing in glibc? getconf GNU_LIBPTHREAD_VERSION gives NPTL 2.19 -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[v8-users] Re: clang vs gcc
the platform is is ubuntu 14.10 x64 Am Sonntag, 29. März 2015 14:46:24 UTC+2 schrieb roiber: > > Hello, > > the default compiler for v8 is clang. Does that mean that i have to > compile my project where i embed v8 in also has to be compiled with clang? > > thanks > roiber > -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[v8-users] clang vs gcc
Hello, the default compiler for v8 is clang. Does that mean that i have to compile my project where i embed v8 in also has to be compiled with clang? thanks roiber -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [v8-users] Re: Move V8 Context from one Isolate to another
Thank you for the good idea. This approach with JSON sounds like what I need to accomplish my task. 2015-03-05 23:44 GMT+02:00 Flying Jester : > What exactly are you trying to accomplish with this? > > Copying a context would be a huge operation, if it's possible at all (I > don't think it is). > > You are almost certainly better off encapsulating the state you want in > JSON or through some API you come up with yourself, and then loading that > in a new context. > > On Thursday, March 5, 2015 at 8:58:45 AM UTC-9, Ivan P. wrote: >> >> What about making copy/clone of context? >> >> 4 бер. 2015 09:52, користувач "Yang Guo" написав: >> > >> > A context is too deeply entangled into the isolate it belongs to, so >> moving the context but not the isolate is basically impossible with the >> current V8. >> > >> > >> > On Sunday, March 1, 2015 at 9:29:49 PM UTC+1, Ivan P. wrote: >> >> >> >> Does anybody know - is there an easy way to move some v8::Conext that >> belongs to some v8::Isolate to another v8::Isolate, preserving complete >> current state? >> >> Or at least make its copy/clone in the another v8::Isolate. >> > >> > -- >> > -- >> > v8-users mailing list >> > v8-u...@googlegroups.com >> > http://groups.google.com/group/v8-users >> > --- >> > You received this message because you are subscribed to a topic in the >> Google Groups "v8-users" group. >> > To unsubscribe from this topic, visit https://groups.google.com/d/ >> topic/v8-users/Hy-Z-i52K8I/unsubscribe. >> > To unsubscribe from this group and all its topics, send an email to >> v8-users+u...@googlegroups.com. >> > For more options, visit https://groups.google.com/d/optout. >> > -- > -- > v8-users mailing list > v8-users@googlegroups.com > http://groups.google.com/group/v8-users > --- > You received this message because you are subscribed to a topic in the > Google Groups "v8-users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/v8-users/Hy-Z-i52K8I/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > v8-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [v8-users] Problems building on ubuntu x86
It is mandatory when you need to croscompile for ARM on 32 bit system where
CXX and LINK are already pointing to the ARM compiler. So making the right
32bit clang executable for CXX(host) is mandatory - at least for those who
lost faith not being able to compile for ARM on the 32 bit linux.
On Friday, March 13, 2015 at 10:41:00 AM UTC+1, Jakob Kummerow wrote:
>
> make ia32.release GYPFLAGS=-Dclang=0 should be enough to fall back to the
> system toolchain. (Maybe we should expose that as a Makefile option... but
> then it's rarely needed.)
>
> On Fri, Mar 13, 2015 at 9:40 AM, Jochen Eisinger > wrote:
>
>> The clang binary included with v8 is a 64bit binary.
>>
>> If you want to compile on a 32bit host, you have to provide your own
>> compiler (by specifying CC, CXX, CPP, and LINK variables to make)
>>
>> best
>> -jochen
>>
>> On Thu, Mar 12, 2015 at 2:04 PM David Xanatos > > wrote:
>>
>>> i have problems building the v8 engine on ubuntu x86
>>>
>>> i get strange errors
>>>
>>> david@ubuntu:~/test/v8$ make ia32.release library=shared
>>> PYTHONPATH="/home/david/test/v8/tools/generate_shim_headers:/home/david/test/v8/build::/home/david/test/v8/build/gyp/pylib:"
>>>
>>> \
>>> GYP_GENERATORS=make \
>>> build/gyp/gyp --generator-output="out" build/all.gyp \
>>> -Ibuild/standalone.gypi --depth=. \
>>> -Dv8_target_arch=ia32 \
>>>\
>>>\
>>> -S.ia32.release -Dcomponent=shared_library
>>> -Dv8_enable_backtrace=1 -Darm_fpu=default -Darm_float_abi=default
>>> make[1]: Entering directory `/home/david/test/v8/out'
>>> CC(target)
>>> /home/david/test/v8/out/ia32.release/obj.target/icudata/third_party/icu/linux/icudtl_dat.o
>>> /home/david/test/v8/third_party/llvm-build/Release+Asserts/bin/clang: 1:
>>> /home/david/test/v8/third_party/llvm-build/Release+Asserts/bin/clang: @8:
>>> not found
>>> /home/david/test/v8/third_party/llvm-build/Release+Asserts/bin/clang: 1:
>>> /home/david/test/v8/third_party/llvm-build/Release+Asserts/bin/clang:
>>> cannot open j
>>>
>>>
>>>
>>> q��zi� d� v��GX.� 0@ y 2 0*p!: No such file
>>> /home/david/test/v8/third_party/llvm-build/Release+Asserts/bin/clang: 2:
>>> /home/david/test/v8/third_party/llvm-build/Release+Asserts/bin/clang: B� �
>>> : not found
>>> /home/david/test/v8/third_party/llvm-build/Release+Asserts/bin/clang: 1:
>>> /home/david/test/v8/third_party/llvm-build/Release+Asserts/bin/clang: ELF :
>>> not found
>>> /home/david/test/v8/third_party/llvm-build/Release+Asserts/bin/clang: 1:
>>> /home/david/test/v8/third_party/llvm-build/Release+Asserts/bin/clang: �:
>>> not found
>>> /home/david/test/v8/third_party/llvm-build/Release+Asserts/bin/clang: 2:
>>> /home/david/test/v8/third_party/llvm-build/Release+Asserts/bin/clang: Q !
>>> �MQ�k�P@��PD @2�� ��@� : not found
>>> /home/david/test/v8/third_party/llvm-build/Release+Asserts/bin/clang: 3:
>>> /home/david/test/v8/third_party/llvm-build/Release+Asserts/bin/clang: @ !
>>> �@$��� : not found
>>> /home/david/test/v8/third_party/llvm-build/Release+Asserts/bin/clang: 1:
>>> /home/david/test/v8/third_party/llvm-build/Release+Asserts/bin/clang: � :
>>> not found
>>> /home/david/test/v8/third_party/llvm-build/Release+Asserts/bin/clang: 1:
>>> /home/david/test/v8/third_party/llvm-build/Release+Asserts/bin/clang: �� �
>>> �@: not found
>>> /home/david/test/v8/third_party/llvm-build/Release+Asserts/bin/clang: 3:
>>> /home/david/test/v8/third_party/llvm-build/Release+Asserts/bin/clang: � :
>>> not found
>>> /home/david/test/v8/third_party/llvm-build/Release+Asserts/bin/clang: 8:
>>> /home/david/test/v8/third_party/llvm-build/Release+Asserts/bin/clang: : not
>>> found
>>> /home/david/test/v8/third_party/llvm-build/Release+Asserts/bin/clang: 9:
>>> /home/david/test/v8/third_party/llvm-build/Release+Asserts/bin/clang: A@� R
>>> � : not found
>>> /home/david/test/v8/third_party/llvm-build/Release+Asserts/bin/clang: 1:
>>> /home/david/test/v8/third_party/llvm-build/Release+Asserts/bin/clang: �� :
>>> not found
>>> /home/david/test/v8/third_party/llvm-build/Release+Asserts/bin/clang:
>>> 11: /home/david/test/v8/third_party/llvm-build/Release+Asserts/bin/clang:
>>> @D�E�� a� L @ @�
>>> n : not found
>>> /home/david/test/v8/third_party/llvm-build/Release+Asserts/bin/clang:
>>> 12: /home/david/test/v8/third_party/llvm-build/Release+Asserts/bin/clang:
>>> Syntax error: "(" unexpected
>>> make[1]: ***
>>> [/home/david/test/v8/out/ia32.release/obj.target/icudata/third_party/icu/linux/icudtl_dat.o]
>>>
>>> Error 2
>>> make[1]: Leaving directory `/home/david/test/v8/out'
>>> make: *** [ia32.release] Error 2
>>> david@ubuntu:~/test/v8$
>>>
>>>
>>>
>>> on ubuntu x64 all works as it should
>>>
>>> whats wrong here?
>>>
>>> --
>>> --
>>> v8-users maili
