Closed GoogleCodeExporter closed 8 years ago
Identical results:
In file included from src/Engine.cpp:12:0:
src/AST.h: In member function ‘bool CAstVariable::is_possibly_eval() const’:
src/AST.h:133:70: error: no matching function for call to
‘v8::internal::Variable::is_possibly_eval()’
src/AST.h:133:70: note: candidate is:
In file included from /home/s/src/client/v8/src/ast.h:43:0,
from /home/s/src/client/v8/src/scopes.h:31,
from src/V8Internal.h:10,
from src/Engine.cpp:5:
/home/s/src/client/v8/src/variables.h:133:8: note: bool
v8::internal::Variable::is_possibly_eval(v8::internal::Isolate*) const
/home/s/src/client/v8/src/variables.h:133:8: note: candidate expects 1
argument, 0 provided
src/Engine.cpp: In member function ‘void
CScript::visit(boost::python::api::object, CScript::LanguageMode) const’:
src/Engine.cpp:529:58: error: ‘class v8::internal::Context’ has no member
named ‘data’
error: command 'gcc' failed with exit status 1
s@ubuntu:~/src/client/pyv8$ svn info
Path: .
Working Copy Root Path: /home/s/src/client/pyv8
URL: http://pyv8.googlecode.com/svn/trunk
Repository Root: http://pyv8.googlecode.com/svn
Repository UUID: 3b770cb8-f9e6-11dd-ac5b-dfceb64ead24
Revision: 450
Node Kind: directory
Schedule: normal
Last Changed Author: flier.lu@gmail.com
Last Changed Rev: 450
Last Changed Date: 2012-10-14 08:32:50 -0700 (Sun, 14 Oct 2012)
s@ubuntu:~/src/client/v8$ svn info
Path: .
Working Copy Root Path: /home/s/src/client/v8
URL: http://v8.googlecode.com/svn/trunk
Repository Root: http://v8.googlecode.com/svn
Repository UUID: ce2b1a6d-e550-0410-aec6-3dcde31c8c00
Revision: 13019
Node Kind: directory
Schedule: normal
Last Changed Author: mstarzinger@chromium.org
Last Changed Rev: 13002
Last Changed Date: 2012-11-19 07:39:24 -0800 (Mon, 19 Nov 2012)
Original comment by mikeasi...@gmail.com
on 20 Nov 2012 at 5:24
Other warnings and errors if trying to compile against V8 r13052
In file included from src/Engine.cpp:12:0:
src/AST.h: In member function ‘bool CAstVariable::is_possibly_eval() const’:
src/AST.h:133:70: error: no matching function for call to
‘v8::internal::Variable::is_possibly_eval()’
/home/buffer/v8/src/variables.h:133:8: note: candidate is: bool
v8::internal::Variable::is_possibly_eval(v8::internal::Isolate*) const
src/AST.h: In member function ‘virtual void
CAstVisitor::VisitModuleStatement(v8::internal::ModuleStatement*)’:
src/AST.h:708:3: error: ‘CAstModuleStatement’ was not declared in this scope
src/AST.h: In member function ‘virtual void
CAstObjectCollector::VisitModuleStatement(v8::internal::ModuleStatement*)’:
src/AST.h:718:3: error: ‘CAstModuleStatement’ was not declared in this scope
src/AST.h: In member function ‘virtual void
CAstListCollector::VisitModuleStatement(v8::internal::ModuleStatement*)’:
src/AST.h:739:3: error: ‘CAstModuleStatement’ was not declared in this scope
src/Engine.cpp: In member function ‘void
CScript::visit(boost::python::api::object, CScript::LanguageMode) const’:
src/Engine.cpp:529:58: error: ‘class v8::internal::Context’ has no member
named ‘data’
src/Engine.cpp: In static member function ‘static v8::Handle<v8::Value>
CPythonExtension::CallStub(const v8::Arguments&)’:
src/Engine.cpp:567:82: warning: ‘static void*
v8::External::Unwrap(v8::Handle<v8::Value>)’ is deprecated (declared at
/home/buffer/v8/include/v8.h:4684)
error: command 'x86_64-pc-linux-gnu-g++' failed with exit status 1
Original comment by angelo.d...@gmail.com
on 26 Nov 2012 at 11:42
Thoughts on changing the behavior of setup.py away from grabbing the latest V8
from svn to instead grabbing a known-working revision? V8 moves a lot faster
than PyV8, and working with a known revision could prevent this kind of
breakage until changes are made to support the moving API target.
Original comment by joel...@gmail.com
on 26 Nov 2012 at 5:58
Please upgrade to PyV8 SVN trunk code after r453, thanks
Original comment by flier...@gmail.com
on 27 Nov 2012 at 3:42
I confirm that r453 fixes the issue. Thanks.
Original comment by angelo.d...@gmail.com
on 27 Nov 2012 at 6:55
Also confirm that this fixes the compilation issue. Now pyv8 fails during test
execution (will file separately)
Original comment by mikeasi...@gmail.com
on 27 Nov 2012 at 4:45
Original comment by flier...@gmail.com
on 28 Nov 2012 at 8:28
Original issue reported on code.google.com by
angelo.d...@gmail.com
on 18 Nov 2012 at 7:09