It does look like "descent_two_isogeny" is what it is failing to compile, but I really can't help without more information. Is there a way to get gcc to print out why it's failing?
It occurs to me that this depends on ratpoints, which has some issues compiling with earlier versions of gcc. What version are you using? On Mon, Jan 4, 2010 at 3:41 AM, John Cremona <john.crem...@gmail.com> wrote: > It seems to be failing while compiling the cython code introduced by > #6583, so perhaps Robert Miller can help? > ... >> gcc -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall >> -Wstrict-prototypes -fPIC -I/usr/local/sage/local/include/FLINT/ >> -I/usr/local/sage/local//include >> -I/usr/local/sage/local//include/csage >> -I/usr/local/sage/devel//sage/sage/ext >> -I/usr/local/sage/local/include/python2.6 -c >> sage/schemes/elliptic_curves/descent_two_isogeny.c -o >> build/temp.linux-i686-2.6/sage/schemes/elliptic_curves/descent_two_isogeny.o >> -std=c99 -w >> error: command 'gcc' failed with exit status 1 -- Robert L. Miller http://www.rlmiller.org/ -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org