Differences between revisions 71 and 75 (spanning 4 versions)
⇤ ← Revision 71 as of 2009-04-21 23:29:26 →
Size: 1173
Editor: MichaelAbshoff
Comment: Move list of spkg to its own subpage.
← Revision 75 as of 2009-05-14 11:57:33 → ⇥
Size: 1566
Editor: MichaelAbshoff
Comment: add link to Sage 4.0 status page
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
 * [[/sage-4.0|Sage 4.0 notes]]
 * [[/sage-3.4.2|Sage 3.4.2 notes]] - this is outdated
Line 24: Line 26:
 * Sage 3.4: segfaults at startup due to libSingular problems (it is basically the same segfault that happened on exit in Sage 3.3)  * Sage 3.4.2: Builds out of the box, but needs various patches to start up and pass all but one doctest - see [[/sage-3.4.2|Sage 3.4.2 notes]].
Line 27: Line 29:
  * segfaults at startup due to libSingular problems - same issue as above   * segfaults at startup due to libSingular problems - same issue as above. Relevant ticket: #5839. This ticket does not fix the problem, but exposes other race conditions in the dealloc code in libSingular on x86-64, i.e. sage.math
 * Sage 3.4: segfaults at startup due to libSingular problems (it is basically the same segfault that happened on exit in Sage 3.3)

OSX 64-bit

This page is about the seemingly endless port of Sage to 64 bit OSX. Here is a list of build notes for various releases:

Note that it is possible to get Sage working to some extend, but it would be nice to get this port done once and for all. The main problem is for Sage to pass all of its doctests.

Build Instructions

The fortran.spkg shipped with Sage does not work. So, unpack the sources, delete the fortan spkg and drop in

Then:

  • export SAGE64=yes
  • make

Known Problems

  • Sage 3.4.2: Builds out of the box, but needs various patches to start up and pass all but one doctest - see Sage 3.4.2 notes.

  • Sage 3.4.1:
    • FLINT.spkg fails to build due to buglet in spkg-check. A fix is at #5817
    • segfaults at startup due to libSingular problems - same issue as above. Relevant ticket: #5839. This ticket does not fix the problem, but exposes other race conditions in the dealloc code in libSingular on x86-64, i.e. sage.math
  • Sage 3.4: segfaults at startup due to libSingular problems (it is basically the same segfault that happened on exit in Sage 3.3)

spkg status

The following has been moved to a subpage here.