On Jan 12, 2:17 pm, adrian <nihilalienumcr...@gmail.com> wrote:

Hi Adrian,

> I just asked the system administrator, and we do have an ultra sparc
> IV.  And thus we could try a binary.

I just check and I am building Sage on the following Sparc:

System Configuration: Sun Microsystems  sun4u Sun Blade 2500
System clock frequency: 160 MHZ
Memory size: 4GB

==================================== CPUs
====================================
               E$          CPU                    CPU
CPU  Freq      Size        Implementation         Mask    Status
Location
---  --------  ----------  ---------------------  -----   ------
--------
0    1280 MHz  1MB         SUNW,UltraSPARC-IIIi    2.4    on-line
MB/0
1    1280 MHz  1MB         SUNW,UltraSPARC-IIIi    2.4    on-line
MB/1

So a US VI shouldn't be needed and I assume the binary would run on
anything that is US III compatible.


> That would be great!
>
> Peace.
> -Adrian.

I spend some of yesterday with building a gcc 4.3.2 based toolchain
for Solaris 10/x86 and now the numpy/scipy issues are gone and I am
down to the following doctest failures:

        sage -t  devel/sage/sage/coding/code_bounds.py # 2 doctests
failed
        sage -t  devel/sage/sage/combinat/schubert_polynomial.py # 0
doctests failed
        sage -t  devel/sage/sage/interfaces/lisp.py # 1 doctests
failed
        sage -t  devel/sage/sage/interfaces/singular.py # 1 doctests
failed
        sage -t  devel/sage/sage/libs/pari/gen.pyx # 2 doctests failed
        sage -t  devel/sage/sage/libs/symmetrica/sc.pxi # Segfault
        sage -t  devel/sage/sage/libs/symmetrica/sb.pxi # 0 doctests
failed
        sage -t  devel/sage/sage/plot/plot.py # 2 doctests failed
        sage -t  devel/sage/sage/rings/polynomial/
polynomial_element.pyx # 1 doctests failed
        sage -t  devel/sage/sage/symbolic/expression.pyx # 1 doctests
failed
        sage -t  devel/sage/sage/tests/book_stein_modform.py # 3
doctests failed

All of the above boils down to a couple bugs:

 * symmetrica interface issues
 * pexpect oddities
 * pow() behaving different for negative values when exponent is non-
integral
 * clib issues - inf vs. Infinity
 * pari + huge malloc (2TB+) segfaults at exit *after* passing the
test after failing the alloc

At least for the pow() issue as well as "inf vs. infinity" I have
workarounds/fixes in mind, so expect the number to go down soon :)

Cheers,

Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to