FS#62952 - [rust] build doesn't respect MAKEFLAGS
Attached to Project:
Arch Linux
Opened by Andreas Baumann (andreas_baumann) - Thursday, 20 June 2019, 11:35 GMT
Last edited by Johannes Löthberg (demize) - Monday, 24 February 2020, 19:09 GMT
Opened by Andreas Baumann (andreas_baumann) - Thursday, 20 June 2019, 11:35 GMT
Last edited by Johannes Löthberg (demize) - Monday, 24 February 2020, 19:09 GMT
|
Details
Description:
python ./x.py build -j"$(nproc)" So, if I run a build slave and want to limit the parallelism with MAKEFLAGS, then this is ignored and my machine gets hell of a load. :-) This leads to another issue, MAKEFLAGS is read by 'make' only, so what about: - ninja - meson - "fill in the new shiny build tool of the day" Additional info: * package version(s): 1.35.0-1 Steps to reproduce: Build the package, look at top. :-) |
This task depends upon
Closed by Johannes Löthberg (demize)
Monday, 24 February 2020, 19:09 GMT
Reason for closing: Not a bug
Additional comments about closing: rustbuild is not make, so I will not pass $MAKEFLAGS to it.
Until either makepkg gets some way to specify the number of jobs generically, or until upstream decides to implement a subset of $MAKEFLAGS parsing, nothing can really change here.
Monday, 24 February 2020, 19:09 GMT
Reason for closing: Not a bug
Additional comments about closing: rustbuild is not make, so I will not pass $MAKEFLAGS to it.
Until either makepkg gets some way to specify the number of jobs generically, or until upstream decides to implement a subset of $MAKEFLAGS parsing, nothing can really change here.
Comment by
Andreas Baumann (andreas_baumann) -
Thursday, 20 June 2019, 12:52 GMT
See also discussion in
https://mirror.archlinux32.org/irc-logs/%23archlinux32/2019-06-20.html#13:36:27