Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Sage build critical path
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  1 message - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Jeroen Demeyer  
View profile  
 More options Sep 4 2012, 8:59 am
From: Jeroen Demeyer <jdeme...@cage.ugent.be>
Date: Tue, 04 Sep 2012 14:59:32 +0200
Local: Tues, Sep 4 2012 8:59 am
Subject: Sage build critical path
Purely for information, this is the critical path for building Sage in
parallel using "make -j" (unlimited number of jobs).  This is after
applying #13392 (remove GNUTLS-related packages).

prereq
bzip2
patch
termcap
readline
sqlite
python
atlas
r
rpy2

By far the most time taken is taken by R and ATLAS, with Python in a
firm third place.

With #13395 (fix upgrading), this list would become slightly longer:

prereq
bzip2
patch
termcap
readline
sqlite
python
mercurial
sage_root
lapack
atlas
r
rpy2


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »