1 | initial version |
The most usual way to build Sage is to unpack the tarball, optionally
set MAKE='make -jN'
with N
of your choice (usually 2, 4, 8
depending on the number of cpu cores available), and run make
.
Running make test
, make ptest
, make testong
or make ptestlong
is an extra step to check whether all examples and tests in Sage's
documentation give the expected output. Not every one goes to that
trouble.
Setting SAGE_CHECK
is an even further step whose effect is,
for each package shipped by Sage, to run the tests provided by that
package (independent of Sage). I would guess that even less people
set SAGE_CHECK
than run make ptestlong
.
Thanks for caring, and please report any bugs you encounter.
2 | No.2 Revision |
The most usual way to build Sage is to unpack the tarball, optionally
set MAKE='make -jN'
with N
of your choice (usually 2, 4, 8
depending on the number of cpu cores available), and run make
.
Running make test
, make ptest
, make
or testongtestlongmake ptestlong
is an extra step to check whether all examples and tests in Sage's
documentation give the expected output. Not every one goes to that
trouble.
Setting SAGE_CHECK
is an even further step whose effect is,
for each package shipped by Sage, to run the tests provided by that
package (independent of Sage). I would guess that even less people
set SAGE_CHECK
than run make ptestlong
.
Thanks for caring, and please report any bugs you encounter.