[sage-devel] Re: Sage 4.1.1.rc1 build halt

2009-08-23 Thread David Joyner
Sage is now building from source on 64bit ubuntu karmic, under the latest (alpha 4?) release! On Wed, Aug 5, 2009 at 8:12 PM, J Elaych 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

[sage-devel] Re: Sage 4.1.1.rc1 build halt

2009-08-07 Thread Peter Jeremy
On 2009-Aug-06 21:11:14 +0100, "Dr. David Kirkby" wrote: >In theory, setting > >CC=/path/to/what/C/compiler/you/want >CXX=/path/to/what/C++/compiler/you/want >SAGE_FORTRAN=/path/to/what/Fortran/compiler/you/want > >should allow you to use any gcc. > >But in practice I don't think it will. I've tr

[sage-devel] Re: Sage 4.1.1.rc1 build halt

2009-08-06 Thread David Joyner
On Thu, Aug 6, 2009 at 10:32 PM, William Stein wrote: > > > 2009/8/6 David Joyner >> >> I tried >> >> export CC=/usr/bin/gcc-3.4 >> export CXX=/usr/bin/cpp-3.4 >> >> then removing the links gcc, cpp and relinking with >> >> sudo ln -s /usr/bin/gcc-3.4 /usr/bin/gcc >> sudo ln -s /usr/bin/cpp-3.4 /

[sage-devel] Re: Sage 4.1.1.rc1 build halt

2009-08-06 Thread William Stein
2009/8/6 David Joyner > > I tried > > export CC=/usr/bin/gcc-3.4 > export CXX=/usr/bin/cpp-3.4 > > then removing the links gcc, cpp and relinking with > > sudo ln -s /usr/bin/gcc-3.4 /usr/bin/gcc > sudo ln -s /usr/bin/cpp-3.4 /usr/bin/cpp > > The build failed at matplotlib. One error was that c++

[sage-devel] Re: Sage 4.1.1.rc1 build halt

2009-08-06 Thread David Joyner
I tried export CC=/usr/bin/gcc-3.4 export CXX=/usr/bin/cpp-3.4 then removing the links gcc, cpp and relinking with sudo ln -s /usr/bin/gcc-3.4 /usr/bin/gcc sudo ln -s /usr/bin/cpp-3.4 /usr/bin/cpp The build failed at matplotlib. One error was that c++ was not installed on the system. On Thu,

[sage-devel] Re: Sage 4.1.1.rc1 build halt

2009-08-06 Thread Dr. David Kirkby
J Elaych wrote: >> 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. >> >> > > Good question, and I hope somebody else can improve my response. > I didn't find a gcc switc

[sage-devel] Re: Sage 4.1.1.rc1 build halt

2009-08-06 Thread J Elaych
> > 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. > > Good question, and I hope somebody else can improve my response. I didn't find a gcc switching tool like I've used

[sage-devel] Re: Sage 4.1.1.rc1 build halt

2009-08-06 Thread David Joyner
On Wed, Aug 5, 2009 at 9:34 PM, J Elaych 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

[sage-devel] Re: Sage 4.1.1.rc1 build halt

2009-08-05 Thread J Elaych
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 ba

[sage-devel] Re: Sage 4.1.1.rc1 build halt

2009-08-05 Thread William Stein
On Wed, Aug 5, 2009 at 5:12 PM, J Elaych 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 th