Sage merely invokes pip to build scipy from source. Indeed, apart from ninja paralellism there is meson parallelism, which is controlled by JOBS env. variable (?). Note that JOBS should be just a number.
On Thursday, September 12, 2024 at 10:29:10 AM UTC+1 oscar.j....@gmail.com wrote: > On Thu, 12 Sept 2024 at 09:31, Dima Pasechnik <dim...@gmail.com> wrote: > > > > scipy itself is not built with configure/make, it's built with meson, > ... > > There is no direct way to specify a non-default "-j" value, however it > appears to be possible to do this via meson, > > which invokes ninja via "meson compile". > > How exactly does sage invoke the SciPy build? > > It should be possible to pass -j through to the backend: > > > https://meson-python.readthedocs.io/en/latest/how-to-guides/meson-args.html#how-to-guides-meson-args > > If Sage's make is already using parallelisation you probably want -j1 > when building SciPy. > > -- > Oscar > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-support/bbf9733b-8dd1-4cb8-9e6e-886e89bd5c69n%40googlegroups.com.