Hi,
I can't compile sage with an up-to-date Debian unstable, and this seems
related to gcc 4.7.1-8 (reverting to 4.7.1-7 does the trick).
I am not sure how to proceed right now, because I have no knowledge of the
sage source code, nor of gcc internals...
Here are a few relevant lines from the compilation logs :
building 'sage.rings.complex_double' extension
building 'sage.rings.polynomial.polynomial_element' extension
building 'sage.rings.polynomial.pbori' extension
building 'sage.rings.polynomial.real_roots' extension
building 'sage.symbolic.constants_c' extension
building 'sage.symbolic.expression' extension
Executing 6 commands (using 1 thread)
gcc -fno-strict-aliasing -fwrapv -DNDEBUG -g -fwrapv -O3 -Wall
-Wstrict-prototypes -fPIC -I/storage/soft/sage-5.3/local/include
-I/storage/soft/sage-5.3/local/include/csage
-I/storage/soft/sage-5.3/devel/sage/sage/ext
-I/storage/soft/sage-5.3/local/include/python2.7 -c
sage/rings/complex_double.c -o
build/temp.linux-x86_64-2.7/sage/rings/complex_double.o -std=c99 -D_XPG6 -w
sage/rings/complex_double.c: In function
'__pyx_t_double_complex_from_parts':
sage/rings/complex_double.c:17514:16: internal compiler error: in
gimplify_expr, at gimplify.c:7592
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.7/README.Bugs> for instructions.
Preprocessed source stored into /tmp/cctiZhpd.out file, please attach this
to your bugreport.
I have a copy of the end of the compilation log file and also of the
temporary file refered to by gcc. Should I get in touch with the gcc team
through a bug report myself? Or open a bug on the Debian side? Or transmit
the files to sage dev team who would then take care of this?
Many thanks in advance
Damien