|
Size: 3189
Comment:
|
← Revision 55 as of 2022-04-05 02:08:12 ⇥
Size: 0
Comment: outdated
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = Getting Sage-3.0.4 to build and pass all tests on Skynet = Tarballs are here: http://sage.math.washington.edu/home/was/tmp To get from rc0 to rc1 from within a built sage do this: {{{ sage: hg_sage.apply('http://sage.math.washington.edu/home/was/patches/a.hg') sage: hg_sage.merge() sage: hg_sage.ci() }}} Then do "./sage -br" at the prompt. == eno: x86_64-Linux-fc8 (status: 0/10) == Using gcc-4.3.1: I (william) can't build ntl. I'm totally stuck until getting past this. Fixed by using this environment (put in my .bash_profile): {{{ # From mabshoff if [ `hostname` = "eno" ]; then export PATH=/usr/local/gcc-4.3.1/x86_64-Linux-fc8/bin/:$PATH export LD_LIBRARY_PATH=/usr/local/gcc-4.3.1/x86_64-Linux-fc8/lib64:/usr/local/gmp-4.2.2/x86_64-Linux-fc8-gcc-4.1.2-rh/lib:/usr/local/mpfr-2.3.1/x86_64-Linux-fc8-gmp-4.2.2-gcc-4.1.2-rh/lib fi }}} == cicero: x86-Linux-fc8 (status: 9/10) == Using gcc-4.1.2: built fine out of the box; all tests for rc1 pass. Using gcc-4.3.1: Mariah gets an "illegal instruction" error when testing {{{ sage -t devel/sage/sage/functions/special.py }}} See http://trac.sagemath.org/sage_trac/ticket/2303 Replicate sage-free: {{{ sage -python >>> import scipy.special; scipy.special.iv(float(1),complex(1,0)) /tmp/foo/sage-3.0.4.rc0-x86-Linux-fc8/local/bin/sage-sage: line 359: 2638 Illegal instruction python "$ }}} * Michael suggested upgrading to the newest version of scipy. This is certainly worth a try. == cleo: ia64-Linux-rhel5 (status: 7/10) == Using gcc-4.1.2: Built fine out of the box. Currently testing; many tests have timed out since this machine is so slow. Possible serious singular crash in groups/matrix_gps/matrix_group.py, though it could be a timeout. There is something massively foobar'd about this machine or its file system or something. For example: {{{ [wstein@cleo sage-3.0.4.rc0]$ time ./sage -c "print 1+1" 2 real 0m26.532s user 0m1.447s sys 0m3.224s }}} A 26 second startup time? Ick. Is there something seriously wrong with the build of Python? == iras: ia64-Linux-suse (status: 6/10) == * There is a major bug in flint that freezes doctesting. See http://trac.sagemath.org/sage_trac/ticket/3616 * segmentation fault {{{ sh: line 1: 16098 Segmentation fault /home/wstein/iras/build/sage-3.0.4.rc0/local/bin/python /home/wstein/iras/build/sage-3.0.4.rc0/tmp/.doctest_totallyreal.py >/tmp/tmpW-loSD 2>/tmp/tmp8ZjloU sage -t devel/sage/sage/rings/number_field/totallyreal.py A mysterious error (perphaps a memory error?) occurred, which may have crashed doctest. }}} I think this is related to the valgrind issues that mabshoff observed and reported. == menas: x86_64-Linux-suse (status: 9/10) == With gcc-4.2.1 and reverting to the old version of clisp all tests pass for sage-4.3.1.rc0: {{{ sage -i clisp-2.41.p14.spkg sage -f maxima-5.13.0.p2.spkg }}} Without reverting clisp, maxima hangs on certain integrals. I think reverting clisp will be ok for this architecture and for this release since the only reason for the new version was build support on more architectures. |
