On Wed, Aug 5, 2009 at 9:34 PM, J Elaych<microsc...@gmail.com> wrote: > > I went into spkg/build and tried different flags. Surprisingly > with MAKE=make it systematically died at the same place, > base3.c, but with MAKE="make -j2" it continued on until > it reached init.c, and stopped there. Ubuntu is updating > gcc-4.4 just about every day, so maybe soon it will work. > > I backed out of gcc-4.4 and pointed gcc -> gcc-4.3, and sure > enough the sage build has passed through pari just fine. > I'd be interested in other Ubuntu user's experiments with > gcc-4.4.
I just upgraded to karmic and the exact same thing happened. Please tell me (in terms an idiot can understand:-) how to get the Sage make command to use a different gcc. > > > On Aug 5, 5:19 pm, William Stein <wst...@gmail.com> wrote: >> On Wed, Aug 5, 2009 at 5:12 PM, J Elaych <microsc...@gmail.com> wrote: >> >> > I'm on Ubuntu 9.10 beta with amd64 x2 and the >> > gcc version 4.4.1 (Ubuntu 4.4.1-1ubuntu1). The >> > build just stops at base3, for hours so far, though >> > 'top' shows cc1 using 99% cpu. I can't find any >> > related info by searching the group but that doesn't >> > mean there isn't a fix. Does anybody have any >> > suggestions about how I might muck around with >> > my compilers on Ubuntu? >> >> > Here's the latest terminal window: >> >> > ... >> > cd ../src/desc && /usr/bin/perl gen_proto highlevel pari.desc > >> > highlvl-linux-x86_64-29561.tmp >> > mv ../src/desc/highlvl-linux-x86_64-29561.tmp ../src/gp/highlvl.h >> > gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. - >> > I../src/headers -DDL_DFLT_NAME=NULL -o highlvl.o ../src/gp/highlvl.c >> > gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. - >> > I../src/headers -o whatnow.o ../src/gp/whatnow.c >> > gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. - >> > I../src/headers -I../src/graph -o plotport.o ../src/graph/plotport.c >> > gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. - >> > I../src/headers -o plotnull.o ../src/graph/plotnull.c >> > cat ../src/kernel/gmp/mp.c ../src/kernel/none/cmp.c ../src/kernel/none/ >> > gcdll.c ../src/kernel/none/ratlift.c ../src/kernel/none/invmod.c ../ >> > src/kernel/gmp/gcd.c ../src/kernel/none/mp_indep.c ../src/kernel/none/ >> > add.c > mp.c >> > gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -fPIC - >> > I. -I../src/headers -I/home/jlh/wrk/sage-4.1.1.rc1/local/include -o >> > mp.o mp.c >> > gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. - >> > I../src/headers -fPIC -o mpinl.o ../src/kernel/none/mpinl.c >> > gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. - >> > I../src/headers -fPIC -o Flx.o ../src/basemath/Flx.c >> > gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. - >> > I../src/headers -fPIC -o Qfb.o ../src/basemath/Qfb.c >> > gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. - >> > I../src/headers -fPIC -o RgX.o ../src/basemath/RgX.c >> > gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. - >> > I../src/headers -fPIC -o alglin1.o ../src/basemath/alglin1.c >> > gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. - >> > I../src/headers -fPIC -o alglin2.o ../src/basemath/alglin2.c >> > gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. - >> > I../src/headers -fPIC -o arith1.o ../src/basemath/arith1.c >> > gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. - >> > I../src/headers -fPIC -o arith2.o ../src/basemath/arith2.c >> > gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. - >> > I../src/headers -fPIC -o base1.o ../src/basemath/base1.c >> > gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. - >> > I../src/headers -fPIC -o base2.o ../src/basemath/base2.c >> > gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. - >> > I../src/headers -fPIC -o base3.o ../src/basemath/base3.c >> >> I have never ever seen or heard of anything like this before, and have no >> clue what could cause this, except a compiler bug. Can you install a more >> stable (or different) version of GCC and use that instead? >> >> -- William > > > --~--~---------~--~----~------------~-------~--~----~ 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 URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
