Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add note about makeflags and ninja parallelism #39128

Open
wants to merge 4 commits into
base: develop
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -341,6 +341,20 @@ in the Installation Guide.
powerful machines, you might even consider `-j16`, as building with
more jobs than CPU cores can speed things up further.

Alternatively, the `MAKEFLAGS` environment variable can be used.
In this case, only provide the flag itself, for example
`export MAKEFLAGS="-j4"`.

Note that the compilation may nonetheless uses a different number of
threads, because sometimes `ninja` is used.
Unfortunately, [there is no way to control number of jobs `ninja` uses
from environment variables](https://github.com/ninja-build/ninja/issues/1482).
See also https://github.com/sagemath/sage/issues/38950.

If the [Meson build system](https://doc-release--sagemath.netlify.app/html/en/installation/meson)
is used, the number of jobs running in parallel passed to `meson compile` will be respected,
because everything are managed by `ninja`.

To reduce the terminal output during the build, type `export V=0`.
(`V` stands for "verbosity".)

Expand Down
Loading