#4652: [with patch, needs testing] make distutils compile Cython extensions in
parallel
------------------------+---------------------------------------------------
 Reporter:  craigcitro  |        Owner:  craigcitro
     Type:  defect      |       Status:  reopened  
 Priority:  major       |    Milestone:  sage-4.0.1
Component:  build       |   Resolution:            
 Keywords:              |  
------------------------+---------------------------------------------------

Comment(by craigcitro):

 Ok, new version of the code is up. This is done differently than last
 time; rather than patch our python, I'm simply inserting the code in our
 `setup.py`, and calling distutils with the new code '''only''' from Sage.

 So, to test this, do the following:

  * download and apply trac-4652-testing.patch
  * set the env variable `SAGE_PARALLEL_DIST` to anything
  * set the env variable `MAKE` to something like `make -j168` (where 168
 is the number of simultaneous threads you want)
  * `sage -br` or `sage -ba`

 If this seems to work for people, then we can try building Sage from
 scratch with it. (I'm going to try setting my machine to do that overnight
 with `4.0.1.rc2`, I think.) If it works fine, I just want to add a little
 bit of documentation and then I'm happy to have this merged. If it works
 for a release or so, I'll start working on getting '''something''' like
 this upstream. (I have no idea how uphill that battle will be.)

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/4652#comment:9>
Sage <http://sagemath.org/>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to