ftsun / pyv8

Automatically exported from code.google.com/p/pyv8
0 stars 0 forks source link

Error build Ubuntu 13.10 Python 2.7.5+ #211

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. svn checkout http://pyv8.googlecode.com/svn/trunk/ pyv8-read-only
2. cd /opt/sources/pyv8-read-only
2. python setup.py build

What is the expected output? What do you see instead?
../src/checks.h:271:5: note: in expansion of macro âSEMI_STATIC_JOINâ
     SEMI_STATIC_JOIN(__StaticAssertTypedef__, __LINE__)
     ^
../src/checks.h:319:30: note: in expansion of macro âSTATIC_CHECKâ
 #define STATIC_ASSERT(test)  STATIC_CHECK(test)
                              ^
../src/stub-cache.h:332:5: note: in expansion of macro âSTATIC_ASSERTâ
     STATIC_ASSERT(kHeapObjectTagSize == Name::kHashShift);
     ^
make: *** [ia32.release] Error 2

--------------------
INFO: generate DTrace probes.h ...
DEBUG: > dtrace -h -C -s /opt/sources/pyv8-read-only/src/probes.d -o 
/opt/sources/pyv8-read-only/src/probes.h
ERROR: generate DTrace probes.h failed: code=127
DEBUG: /bin/sh: 1: dtrace: not found

INFO: dtrace or systemtap doesn't works, force to disable probes
running build_py
creating build/lib.linux-i686-2.7
copying PyV8.py -> build/lib.linux-i686-2.7
running build_ext
building '_PyV8' extension
creating build/temp.linux-i686-2.7
creating build/temp.linux-i686-2.7/src
i686-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-prototypes -fPIC -DBOOST_PYTHON_STATIC_LIB -DV8_NATIVE_REGEXP 
-DENABLE_DEBUGGER_SUPPORT -I/opt/sources/pyv8-read-only/build/v8/include 
-I/opt/sources/pyv8-read-only/build/v8 
-I/opt/sources/pyv8-read-only/build/v8/src -I/usr/local/include 
-I/usr/include/python2.7 -c src/Utils.cpp -o 
build/temp.linux-i686-2.7/src/Utils.o -Wno-write-strings -g -O3
cc1plus: warning: command line option â-Wstrict-prototypesâ is valid for 
C/ObjC but not for C++ [enabled by default]
i686-linux-gnu-gcc: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
error: command 'i686-linux-gnu-gcc' failed with exit status 4

What version of the product are you using? On what operating system?
root@server:/opt/sources# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=13.10
DISTRIB_CODENAME=saucy
DISTRIB_DESCRIPTION="Ubuntu 13.10"

Linux 3.8.0-19-generic #30-Ubuntu SMP Wed May 1 16:36:13 UTC 2013 i686 i686 
i686 GNU/Linux

Python 2.7.5+ (default, Sep 19 2013, 13:49:51)

Please provide any additional information below.

Original issue reported on code.google.com by addo.del...@gmail.com on 30 Oct 2013 at 12:27

GoogleCodeExporter commented 8 years ago

Original comment by flier...@gmail.com on 31 Oct 2013 at 9:00

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
I have the same problem on Ubuntu 12.04, with Kernel version 3.8.0-32-generic 
('Precise'); Installing the package systemtap-sdt-dev in order to get dtrace 
didn't help.

Original comment by mmueller...@gmail.com on 10 Nov 2013 at 11:15

GoogleCodeExporter commented 8 years ago
To be more precise: Once I installed dtrace using systemtap, the error message 
changed to 
'''
ERROR: generate DTrace probes.o failed: code=1
DEBUG: Assembler messages:
Fatal error: can't create /home/forge/lib/pyv8/build/probes.o: No such file or 
directory

INFO: dtrace or systemtap doesn't works, force to disable probes
'''

Original comment by mmueller...@gmail.com on 10 Nov 2013 at 11:17

GoogleCodeExporter commented 8 years ago
It may caused by GCC 4.7 or later, please try the latest PyV8 SVN trunk code, 
which should make GCC 4.7 happy

Original comment by flier...@gmail.com on 11 Nov 2013 at 6:34

GoogleCodeExporter commented 8 years ago
This has resolved the issue. Thanks a lot for your efforts!

Original comment by mmueller...@gmail.com on 11 Nov 2013 at 9:31

GoogleCodeExporter commented 8 years ago
Sorry, but I continue same error

Original comment by addo.del...@gmail.com on 11 Nov 2013 at 10:58

GoogleCodeExporter commented 8 years ago
hi, addo,

   It seems your compiler crashed, could you try a clean build again? 

i686-linux-gnu-gcc: internal compiler error: Killed (program cc1plus)

What's your OS, Python and GCC version?

Original comment by flier...@gmail.com on 12 Nov 2013 at 2:16

GoogleCodeExporter commented 8 years ago
Thanks your reply.

gcc --version
gcc (Ubuntu/Linaro 4.8.1-10ubuntu8) 4.8.1
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

python --version
Python 2.7.5+

uname -a
Linux lettura 3.8.0-19-generic #30-Ubuntu SMP Wed May 1 16:36:13 UTC 2013 i686 
i686 i686 GNU/Linux

cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=13.10
DISTRIB_CODENAME=saucy
DISTRIB_DESCRIPTION="Ubuntu 13.10"

Original comment by addo.del...@gmail.com on 12 Nov 2013 at 4:34

Attachments: