Closed GoogleCodeExporter closed 9 years ago
V8, rev: 4059
PyV8 rev: 236
Original comment by dcg...@gmail.com
on 9 Mar 2010 at 9:16
I can't reproduce it with debian, v8 v4068 and pyv8 v239.
It seems pyv8 linked with wrong v8 library, could you check the module
extension
file with ldd and nm?
flier@debian:~/pyv8/build/lib.linux-i686-2.5$ ldd _PyV8.so
linux-gate.so.1 => (0xb7fd5000)
libboost_python-py25.so.1.35.0 => /usr/lib/libboost_python-py25.so.1.35.0
(0xb7cd6000)
librt.so.1 => /lib/i686/cmov/librt.so.1 (0xb7ccd000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb7bde000)
libm.so.6 => /lib/i686/cmov/libm.so.6 (0xb7bb8000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb7bab000)
libpthread.so.0 => /lib/i686/cmov/libpthread.so.0 (0xb7b92000)
libc.so.6 => /lib/i686/cmov/libc.so.6 (0xb7a37000)
libutil.so.1 => /lib/i686/cmov/libutil.so.1 (0xb7a33000)
libdl.so.2 => /lib/i686/cmov/libdl.so.2 (0xb7a2e000)
/lib/ld-linux.so.2 (0xb7fd6000)
flier@debian:~/pyv8/build/lib.linux-i686-2.5$ nm _PyV8.so | grep
8internal3Log14output_buffer
0029cdc4 b _ZN2v88internal3Log14output_buffer_E
Original comment by flier...@gmail.com
on 9 Mar 2010 at 7:15
maybe he build v8 engine NOT as static library
Original comment by tocer.deng@gmail.com
on 31 Mar 2010 at 9:08
I agree, I also guess the v8 library will be the root cause.
Original comment by flier...@gmail.com
on 31 Mar 2010 at 9:11
Original comment by flier...@gmail.com
on 9 Apr 2010 at 9:57
Original issue reported on code.google.com by
dcg...@gmail.com
on 9 Mar 2010 at 9:11