Differences between revisions 71 and 72
⇤ ← Revision 71 as of 2009-04-21 23:29:26 →
Size: 1173
Editor: MichaelAbshoff
Comment: Move list of spkg to its own subpage.
← Revision 72 as of 2009-04-22 21:20:23 → ⇥
Size: 1331
Editor: MichaelAbshoff
Comment: add relevant ticket for libSingular problem
Deletions are marked like this. Additions are marked like this.
Line 24: Line 24:
 * Sage 3.4: segfaults at startup due to libSingular problems (it is basically the same segfault that happened on exit in Sage 3.3)
Line 27: Line 26:
  * 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.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.