On Jan 19, 5:39 am, Craig Citro <craigci...@gmail.com> wrote: > So the error seems to be coming from this command: > > > building 'sage.schemes.elliptic_curves.descent_two_isogeny' extension > > /usr/local/gcc-4.4.1-sun-linker/bin/gcc -fno-strict-aliasing -DNDEBUG -g -O3 > > -Wall -Wstrict-prototypes -fPIC > > -I/export/home/drkirkby/sage-4.3.1.rc0/local/include/FLINT/ > > -I/export/home/drkirkby/sage-4.3.1.rc0/local//include > > -I/export/home/drkirkby/sage-4.3.1.rc0/local//include/csage > > -I/export/home/drkirkby/sage-4.3.1.rc0/devel//sage/sage/ext > > -I/export/home/drkirkby/sage-4.3.1.rc0/local/include/python2.6 -c > > sage/schemes/elliptic_curves/descent_two_isogeny.c -o > > build/temp.solaris-2.10-sun4u-2.6/sage/schemes/elliptic_curves/descent_two_isogeny.o > > -std=c99 > > And it's an explicit #error in a header file: > > > In file included from /usr/include/limits.h:18, > > from > > /usr/local/gcc-4.4.1-sun-linker/bin/../lib/gcc/sparc-sun-solaris2.10/4.4.1/include-fixed/limits.h:122, > > from > > /usr/local/gcc-4.4.1-sun-linker/bin/../lib/gcc/sparc-sun-solaris2.10/4.4.1/include-fixed/syslimits.h:7, > > from > > /usr/local/gcc-4.4.1-sun-linker/bin/../lib/gcc/sparc-sun-solaris2.10/4.4.1/include-fixed/limits.h:11, > > from > > /export/home/drkirkby/sage-4.3.1.rc0/local/include/python2.6/Python.h:19, > > from sage/schemes/elliptic_curves/descent_two_isogeny.c:4: > > /usr/local/gcc-4.4.1-sun-linker/bin/../lib/gcc/sparc-sun-solaris2.10/4.4.1/include-fixed/sys/feature_tests.h:341:2: > > error: #error "Compiler or options invalid for pre-UNIX 03 X/Open > > applications and pre-2001 POSIX applications" > > Can you look in that header file, and see what preprocessor tests are > being done that cause it to get included? (Was this on a machine that > we have access to, like t2?) > > -cc
Hi, I'm not in a position to do much today on this, as I'm going to my fathers. I will however have access to the internet, but obviously it would be rude to go to see someone, then spending a lot of time trying to get Sage working. This was not on 't2', but 't2' has the same version of 'gcc', configured the same way, using the exact same operating system (Solaris 10 update 7). So it should be possible to reproduce this on t2. With the exception of a bug in the Solaris implementation of 'memset' on 't2', which has now been patched with a patch from Sun, I've never observed any differece between the behavious on 't2' and my own machine. Dave
-- 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
