469,644 Members | 1,774 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,644 developers. It's quick & easy.

Problem building python in virtual machine running centos

Hi,

I am trying to build python-2.4.5 on Centos 5.1, which is a virtual
machine running with xen.
I am not able to build python. The compilation crash with the following:
gcc -pthread -c -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -I.
-I./Include -DPy_BUILD_CORE -o Objects/unicodeobject.o
Objects/unicodeobject.c
In file included from ./Include/Python.h:76,
from Objects/unicodeobject.c:39:
../Include/object.h:228: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://bugzilla.redhat.com/bugzillafor instructions.
The bug is not reproducible, so it is likely a hardware or OS problem.
Any suggestion of what am I doing wrong?

Thanks
Alex

--
o Alexandre Gillet Ph.D. email: gi****@scripps.edu
/ The Scripps Research Institute,
o Dept. Molecular Biology, MB-5,
\ 10550 North Torrey Pines Road,
o La Jolla, CA 92037-1000, USA.
/ tel: (858) 784-2053
o fax: (858) 784-2860
web: http://mgl.scripps.edu/projects/tangible_models/
Jun 27 '08 #1
3 1766
On 25 Apr, 03:05, Alexandre Gillet <gil...@scripps.eduwrote:
>
I am trying to build python-2.4.5 on Centos 5.1, which is a virtual
machine running with xen.
I am not able to build python. The compilation crash with the following:
gcc -pthread -c -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -I.
-I./Include -DPy_BUILD_CORE -o Objects/unicodeobject.o
Objects/unicodeobject.c
In file included from ./Include/Python.h:76,
from Objects/unicodeobject.c:39:
./Include/object.h:228: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://bugzilla.redhat.com/bugzillafor instructions.
The bug is not reproducible, so it is likely a hardware or OS problem.

Any suggestion of what am I doing wrong?
You say that the bug is not reproducible, so that means that you can
sometimes compile Python, or does the crash always happen when
compiling some file (not necessarily the one mentioned above)? I think
I've only ever seen a reproducible gcc crash once, and that had
something to do with a C++ source file which I then split into two and
was able to compile as these two separate parts. You might want to
check the gcc version (gcc -v) and to look at bug fixes in any later
versions. Generally, if you get an internal error in gcc, you aren't
doing anything wrong yourself.

Paul
Jun 27 '08 #2
Paul Boddie wrote:
On 25 Apr, 03:05, Alexandre Gillet <gil...@scripps.eduwrote:
>>I am trying to build python-2.4.5 on Centos 5.1, which is a virtual
machine running with xen.
I am not able to build python. The compilation crash with the following:
gcc -pthread -c -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -I.
-I./Include -DPy_BUILD_CORE -o Objects/unicodeobject.o
Objects/unicodeobject.c
In file included from ./Include/Python.h:76,
from Objects/unicodeobject.c:39:
./Include/object.h:228: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://bugzilla.redhat.com/bugzillafor instructions.
The bug is not reproducible, so it is likely a hardware or OS problem.

Any suggestion of what am I doing wrong?


You say that the bug is not reproducible, so that means that you can
"The bug is not reproducible, so it is likely a hardware or OS problem."

This line is printed by GCC itself, not the OP

Paul
sometimes compile Python, or does the crash always happen when
compiling some file (not necessarily the one mentioned above)? I think
I've only ever seen a reproducible gcc crash once, and that had
something to do with a C++ source file which I then split into two and
was able to compile as these two separate parts. You might want to
check the gcc version (gcc -v) and to look at bug fixes in any later
versions. Generally, if you get an internal error in gcc, you aren't
doing anything wrong yourself.

Paul
Jun 27 '08 #3
On 25 Apr, 14:16, Paul Melis <p...@science.uva.nlwrote:
>
"The bug is not reproducible, so it is likely a hardware or OS problem."

This line is printed by GCC itself, not the OP
It's a strange thing for anyone to claim in an error message, though,
especially if it is reproducible. Perhaps some people have special
criteria for reproducibility.

Paul
Jun 27 '08 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

29 posts views Thread by Maurice LING | last post: by
2 posts views Thread by Helmut Jarausch | last post: by
24 posts views Thread by Richard Blackwood | last post: by
118 posts views Thread by 63q2o4i02 | last post: by
2 posts views Thread by Chris Miles | last post: by
1 post views Thread by pradipbhosale | last post: by
reply views Thread by Alexandre Gillet | last post: by
4 posts views Thread by Ognjen Bezanov | last post: by
reply views Thread by gheharukoh7 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.