On Tue, Sep 29, 2009 at 11:21 AM, Dr. David Kirkby <david.kir...@onetel.net> wrote: > > I tried to build Sage 4.1.2.alpha4 on a Sun Blade 2000 SPARC with Sun's > compiler. This was on my own machine. I'd expect similar on the Sun > T5240 't2', though there are some cases where there may be additional > problems on 't2'. > > Each time something went wrong, I created a ticket, touched the file > spkg/installed/foobar and carried on. > > Then created a ticket which has links to all the other tickets. > > The table here lists 39 things I am aware of will prevent Sage building > with Sun's compiler. > > http://sagetrac.org/sage_trac/ticket/7056
Wow, that is very nice. I just want to applaud you on a superb use of "metatickets", imho. Now we can easily track progress toward the solaris port in that regard. Bravo!! William > > Most of the reasons for failure fall into a 5 categories. > > 1) The fact the current 'prefreq-0.3' configure script exits if one does > not use gcc is pretty fundamental, but is fixed by > > http://sagetrac.org/sage_trac/ticket/7021 > > which awaits review. > > 2) Many programs do not respect CC, CXX or SAGE_FORTRAN, but use the > first GNU compiler in the path. > > 3) Several programs believe GMP is not installed, despite the fact the > GMP substitute mpir has been installed and the GMP header files and > libraries are all present. > > Other programs do mpir. > > 4) GNU flags passed to Sun compilers. > > 5) Buggy code, the GNU compilers accept, but the Sun compilers will not. > > > Dave > > > > > -- William Stein Associate Professor of Mathematics University of Washington http://wstein.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 -~----------~----~----~----~------~----~------~--~---
