Changes between Initial Version and Version 1 of Ticket #13731, comment 90


Ignore:
Timestamp:
11/29/12 22:09:26 (7 years ago)
Author:
SimonKing
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #13731, comment 90

    initial v1  
    11The [http://sage.math.washington.edu/home/SimonKing/SAGE/spkgs/singular-3-1-5.p2.spkg new Singular spkg] is intended to eventually become a new patch level of the standard Singular spkg.
    22
    3 The spkg is not ready for review yet (for example, SPKG.txt needs to be updated, and there are uncommited changes). But it contains two bug fixes from upstream, it builds on Linux and OSX, and one can ''opionally'' build libsingular and the Singular executable based on xalloc.
     3The spkg is not ready for review yet (for example, SPKG.txt needs to be updated, and there are uncommited changes). But it contains two bug fixes from upstream, it builds on Linux and OSX, and one can ''optionally'' build libsingular and the Singular executable based on xalloc.
    44
    55The disadvantage is that there are much more changes to the upstream sources compared with Nils' spkg. So, it could very well be that in the xalloc version one sees bugs that are actually artefacts of totally stripping down omalloc.
    66
    7 Here  is what happens with the new spkg, build with `export SINGULAR_XALLOC=yes` on my !openSuse laptop:
     7Here  is what happens with the new spkg, build with `export SINGULAR_XALLOC=yes` on my `openSuse` laptop:
    88
    99'''__Without MALLOC_CHECK__'''
     
    5858sage: x*y
    5959x*y
    60 sage:
     60sage: quit
    6161Exiting Sage (CPU time 0m0.05s, Wall time 0m26.09s).
    6262/home/simon/SAGE/debug/sage-5.5.rc0/local/lib/libcsage.so(print_backtrace+0x31)[0x7fcc69d1ac77]