Right now the actual make step that compiles the code is really being triggered by the %{make_install} macro in the %install section. This sort of works, but it has the unintended side-effect that make doesn't use any CPU parallelism. By using %make_build in the %build section, RPM packaging will automatically use the same number of parallel make jobs as the host has CPU parallelism.
LorbusChris
commented
5 years ago
Right now the actual
makestep that compiles the code is really being triggered by the%{make_install}macro in the%installsection. This sort of works, but it has the unintended side-effect that make doesn't use any CPU parallelism. By using%make_buildin the%buildsection, RPM packaging will automatically use the same number of parallel make jobs as the host has CPU parallelism.