Opened 12 years ago

Closed 11 years ago

#1006 closed defect (fixed)

Port Sage to 64 bit OSX 10.5

Reported by: mabshoff Owned by: mabshoff
Priority: major Milestone: sage-3.3
Component: distribution Keywords: Leopard, 64 bit
Cc: Merged in:
Authors: Reviewers:
Report Upstream: Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Description


Change History (7)

comment:1 Changed 12 years ago by mabshoff

  • Status changed from new to assigned

comment:2 Changed 12 years ago by cwitty

When this is fixed, inst/inst.tex should be updated; I just changed that file to say that OS X 10.5 is not yet supported.

comment:3 Changed 12 years ago by mabshoff

  • Milestone changed from sage-2.10.1 to sage-2.10

comment:4 Changed 12 years ago by mabshoff

  • Keywords 64 bit added

A short update: I am tracking progress at http://wiki.sagemath.org/osx64

So far there are a couple problems:

  • libSingular segfaults on import
  • numpy fails to build
  • twistedweb2 depends on some OSX specfic python extensions

Other than that it is mostly supplying the right flags in the build process. I am currently merging those OSX 10.5 64 bit build fixes for every spkg I touch.

Cheers,

Michael

comment:5 Changed 12 years ago by mabshoff

Sage 3.0.2.alpha1 will contain a massive number of fixes. I cannot believe that it has been seven month since we opened this ticket.

Cheers,

Michael

comment:6 Changed 11 years ago by mabshoff

And time marches on: ten months and counting, but 3.1.2 will get us very close to a working OSX 64 bit port. But we need to push hard to get it a fully working port.

Cheers,

Michael

comment:7 Changed 11 years ago by mabshoff

  • Milestone changed from sage-3.4.1 to sage-3.3
  • Resolution set to fixed
  • Status changed from assigned to closed

Provided one uses the new experimental Fortran.spkg Sage 3.3.alpha5 and later build out of the box in 64 bit mode on OSX 10.5. There are some doctesting issues left, but those will be addressed via other tickets.

So I am closing this "meta" ticket - it took way too long to fix this.

Cheers,

Michael

Note: See TracTickets for help on using tickets.