Differences between revisions 1 and 71 (spanning 70 versions)
Revision 1 as of 2007-11-22 05:02:41
Size: 1587
Editor: was
Comment:
Revision 71 as of 2009-04-21 23:29:26
Size: 1173
Comment: Move list of spkg to its own subpage.
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
 * export CFLAGS="-arch x86_64" This page is about the seemingly endless port of Sage to 64 bit OSX. Here is a list of build notes for various releases:
Line 5: Line 5:
 * building python {{{
For some pointers on how to get python to build in 64 bit mode see
 * [[/sage-3.3|Sage 3.3 notes]] - this is outdated
 * [[/sage-3.2.3|Sage 3.2.3 notes]] - this is outdated
 * [[/sage-3.0.2|Sage 3.0.2 notes]] - this is outdated
Line 8: Line 9:
http://mail.python.org/pipermail/pythonmac-sig/2007-June/019045.html 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.
Line 10: Line 11:
To quote (which is actually about 64 bit on *Tiger*): == Build Instructions ==
Line 12: Line 13:
<quote>
The build is universal, but for me only one of the two archictures
actually worked: I did my build on an Intel system and the 64-bit
build worked on that machine, but didn't work on a G5 mac. That's
probably something shallow, but as that machine doesn't have the
Xcode installed and is on the other side of a slow network connection
I haven't tried to debug this yet.
The fortran.spkg shipped with Sage does not work. So, unpack the sources, delete the fortan spkg and drop in
Line 20: Line 15:
1) Edit the configure script, look for "-arch i386" and "-arch ppc"
and change that those to "-arch ppc64" and "-arch x86_64". You'll
have to make multiple changes to the configure file.
 http://sage.math.washington.edu/home/mabshoff/spkgs/fortran-OSX64-20090120.spkg
Line 24: Line 17:
2) Build using: Then:
Line 26: Line 19:
       $ mkdir build
       $ cd build
       $ CFLAGS="-arch ppc64 -arch x86_64" ../configure \
           --enable-universalsdk \
           --disable-toolbox-glue --prefix=/opt/python25-64bit
       $ make
       $ make install
 * export SAGE64=yes
 * make
Line 34: Line 22:
3) Optionally: run "make testall" to run the unittests and check
pyconfig.h to check the various SIZEOF definitions.
== Known Problems ==
Line 37: Line 24:
You now have a 64-bit build of python in /opt/python25-64bit.
}}}
 * 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.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
Line 40: Line 29:
== spkg status ==
Line 41: Line 31:
 * Cython {{{ 20:58 < mabshoff> There is also a bug in the way Cython builds its extensions.
20:58 < mabshoff> It needs to use the flags python was build with, not some random stuff people thing
20:58 < mabshoff> think is good.
20:58 < mabshoff> I told Robert about it.
}}}
The following has been moved to a subpage [[/spkgfixes|here]].

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: segfaults at startup due to libSingular problems (it is basically the same segfault that happened on exit in Sage 3.3)
  • 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

spkg status

The following has been moved to a subpage here.