You mean like https://github.com/sagemath/sage/pull/16 ?
See http://trac.sagemath.org/ticket/15616 as well. This is a good
suggestion.
On Tuesday, December 31, 2013 7:57:17 PM UTC-5, Joseph P. Skudlarek wrote:
>
> This is a request to update the README.txt file used when building from
> source
Yes, that's perfect -- thanks! And thanks for gently showing how easily it
could be done -- much appreciated. /J
On Wednesday, January 1, 2014 10:44:54 AM UTC-8, kcrisman wrote:
>
> You mean like https://github.com/sagemath/sage/pull/16 ? See
> http://trac.sagemath.org/ticket/15616 as well.
It should not be enabled in the top-level make, in my opinion.
Typically, "make -jN" makes parallel compiles within the same package
(if the package supports it). The parallel build in sage compiles
different packages in parallel, but each package still compiles as -j1.
On 01/03/2014 02:48 AM
On 01/03/2014 03:28 PM, Jeroen Demeyer wrote:
On 2014-01-03 01:44, P Purkayastha wrote:
The parallel build in sage compiles
different packages in parallel, but each package still compiles as -j1.
That statement is completely not true. Sage uses both, it compiles
different packages in parallel a
Does the end user care about this distinction? "make -jN" uses N
cores/processes to make whatever it is you're making. Building in
parallel should be standard and encouraged, not buried in some
environment variable.
On Thu, Jan 2, 2014 at 4:44 PM, P Purkayastha wrote:
> It should not be enabled i
On 2014-01-03 01:44, P Purkayastha wrote:
The parallel build in sage compiles
different packages in parallel, but each package still compiles as -j1.
That statement is completely not true. Sage uses both, it compiles
different packages in parallel and also builds the packages itself in
parallel
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
