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 <ppu...@gmail.com> wrote:
> 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, Robert Bradshaw wrote:
>>
>> How hard would it be to let "make -jN" actually work from the top-level
>> make?
>>
>> On Tue, Dec 31, 2013 at 4:57 PM, Joseph P. Skudlarek <jsku...@gmail.com>
>> wrote:
>>>
>>> This is a request to update the README.txt file used when building from
>>> sources -- the README.txt buries the fact that "-jN" in "make -jN" is
>>> effectively ignored -- but it does make claar, in the details below,
>>> that you need <<export MAKE="make -jN">>.
>>>
>>> Since ignoring -jN is non-standard, and since it's important to avoid
>>> surprises when building in parallel, I suggest changing README.txt (at
>>> the top level of the source tree downloaded as sage-6.0.tar.gz) as
>>> follows.
>>>
>>> replace
>>>
>>>      3. cd into the Sage directory and type make:
>>>
>>>             cd sage-*/
>>>             make
>>>
>>>         That's it! Everything is automatic and non-interactive. The build
>>>         should work fine on all fully supported platforms. If it does
>>> not, we
>>>         want to know!
>>>
>>> with
>>>
>>>      3. cd into the Sage directory and type make:
>>>
>>>             cd sage-*/
>>>             make
>>>
>>>         That's it! Everything is automatic and non-interactive. The build
>>>         should work fine on all fully supported platforms. If it does
>>> not, we
>>>         want to know!  If you want to build in parallel, see below.
>>>
>>> []
>>>
>>> Thanks.  /J
>>>
>>> --
>>> 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 sage-support+unsubscr...@googlegroups.com.
>>> To post to this group, send email to sage-support@googlegroups.com.
>>> Visit this group at http://groups.google.com/group/sage-support.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>
> --
> 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 sage-support+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-support@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-support.
> For more options, visit https://groups.google.com/groups/opt_out.

-- 
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 sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to