On 2014-01-03 10:56, P Purkayastha wrote:
Then I am very surprised; for two reasons - I have never seen more than
one gcc process on htop while running a sage compilation with -j2 or -j4
-- maybe it has always just so happened that every time I looked at
htop, it was a package without support for -j.
...or it could mean that make prefers a breadth-first build in which
case building N packages each with 1 job is preferred over building 1
package with N jobs. This actually makes a lot of sense, since the
"configure" step and often the "install" step of packages are done serially.
Secondly, it is nowhere mentioned in the README that both sage packages
and compilation within each individual package are launched as -j.
The README says
3. Extract the Sage source tarball and cd into a directory with no
spaces in it. If you have a machine with 4 processors, say, type
the following to configure the build script to perform a parallel
compilation of Sage using 4 jobs:
which is sufficiently vague that it could mean both kinds of parallelism.
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/groups/opt_out.
