Closed GoogleCodeExporter closed 9 years ago
I'm using a flavor of ubuntu 12.10 with python 2.7.3.
What's causing this issue?
Original comment by rsimmo...@gmail.com
on 6 Dec 2012 at 10:42
This issue is being caused by the current revision of v8. The workaround to
fix this problem is to checkout r13134 of v8. Additionally, make sure to
comment out line 448 in pyv8/setup.py so that pyv8 does not update the v8 code:
#self.checkout_v8()
Original comment by rsimmo...@gmail.com
on 7 Dec 2012 at 4:38
I've got the same problem. In order to build PyV8, I follow this guide:
http://andrewwilkinson.wordpress.com/2012/01/23/integrating-python-and-javascrip
t-with-pyv8/ I've checkedout the r13134 of v8, as you suggested here, but it
doesn't work! Any suggestions?
Original comment by gilberto...@gmail.com
on 8 Dec 2012 at 2:53
Did you comment out self.checkout_v8() ? If not, then you will update v8 to the
new non-working version before building pyv8.
Original comment by rsimmo...@gmail.com
on 8 Dec 2012 at 6:24
Yes, I've commented self.checkout_v8() in setup.py (in pyv8 source code).
Original comment by gilberto...@gmail.com
on 8 Dec 2012 at 6:28
Ah. Perhaps don't follow those directions. Do the following:
svn checkout http://v8.googlecode.com/svn/trunk/@13134 v8
svn checkout http://pyv8.googlecode.com/svn/trunk/ pyv8
Comment out line 448 of pyv8/setup.py: #self.checkout_v8()
export V8_HOME=/path/to/v8
cd pyv8
python setup.py build
sudo python setup.py install
Original comment by rsimmo...@gmail.com
on 8 Dec 2012 at 6:28
Now it works. I suppose the error was in "export PyV8=`pwd`" command. Thank you
for helping me.
Original comment by gilberto...@gmail.com
on 8 Dec 2012 at 6:45
I just attempted to build today and experienced this issue. The easiest
solution I found, given the current v8 code base is to have setup.py checkout
r13261 of v8. If you set V8_SVN_REVISION to 13261, everything seems to work
just fine.
It looks like r13262 was a fairly large change, and the most recent culprit for
these errors.
Original comment by artlo...@gmail.com
on 24 Dec 2012 at 7:27
Original comment by flier...@gmail.com
on 26 Dec 2012 at 7:28
Why does pyv8 require its own private copy of v8 to build against? Can't it be
set to build against an installed version of v8 already on the system?
Original comment by rsimmo...@gmail.com
on 26 Dec 2012 at 6:26
v8 disabled C++ exception and RTTI by default, but boost::python need it
Original comment by flier...@gmail.com
on 27 Dec 2012 at 1:49
I want to continue this, but on the group list. This is offtopic for this
issue report:
https://groups.google.com/forum/?fromgroups=#!topic/pyv8/kp9mM4BZwDY
Original comment by rsimmo...@gmail.com
on 27 Dec 2012 at 2:10
Please verify it with SVN trunk code after r459, thanks
Original comment by flier...@gmail.com
on 31 Dec 2012 at 3:50
I've just been able to build successfully on Mac OS. Thanks for the fix!
Original comment by artlo...@gmail.com
on 4 Jan 2013 at 6:29
Original comment by flier...@gmail.com
on 7 Jan 2013 at 3:06
Original issue reported on code.google.com by
rsimmo...@gmail.com
on 6 Dec 2012 at 10:40