On Sun, Aug 30, 2009 at 11:04 AM, arachnoid <[email protected]> wrote:
> > > > On Aug 30, 8:49 am, William Stein <[email protected]> wrote: > > On Sun, Aug 30, 2009 at 3:04 AM, arachnoid <[email protected]> wrote: > > > > > On a Dell desktop with 2 GB RAM and plenty of free HDD space, Sage > > > compilation fails. Here is the end of the installation log: > > > > What exact compiler are you using (output of gcc -v)? > > $ gcc -v > > Using built-in specs. > Target: i586-redhat-linux > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man -- > infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/ > bugzilla --enable-bootstrap --enable-shared --enable-threads=posix -- > enable-checking=release --with-system-zlib --enable-__cxa_atexit -- > disable-libunwind-exceptions --enable-languages=c,c++,objc,obj-c+ > +,java,fortran,ada --enable-java-awt=gtk --disable-dssi --enable- > plugin --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre -- > enable-libgcj-multifile --enable-java-maintainer-mode --with-ecj-jar=/ > usr/share/java/eclipse-ecj.jar --disable-libjava-multilib --with-ppl -- > with-cloog --with-tune=generic --with-arch=i586 --build=i586-redhat- > linux > Thread model: posix > gcc version 4.4.1 20090725 (Red Hat 4.4.1-2) (GCC) > > > Is there any > > possibility to use a different compiler? > > There is a sense in which a particular Linux distribution is married > to its C/C++ compiler, and use of a different compiler tends to be > limited to cases in which there is little interaction between a > compiled executable and other programs in that same installation, > clearly not true for Sage. Actually, there is little interaction between the compiled Sage and the linux install. Sage is almost self-contained. > Since my first post I have tried this compilation several times on > different machines (all running Fedora 11), and always with the same > result -- at some point, the compilation allocates all available > memory and crashes. > Since you're willing to invest that much energy, I strongly recommend trying a different version of GCC. There is a known bug in PARI or GCC, compiling specifically that file in PARI. Is there an easy command line way to upgrade Fedora 10 to Fedora 11? Our build machines are: wst...@fedora32:~$ cat /etc/issue Fedora release 10 (Cambridge) Kernel \r on an \m (\l) and console access is somewhat painful. William > > Next, I plan to try using distcc during compilation in the hope of > easing the burden on any single machine (I have six). > > > > -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
