I'm currently working on enhancing the Rust package (currently 1.72.0) in OpenWrt (the build system is based on buildroot). After ensuring the x.py command is prefixed with + and that MAKEFLAGS is set correctly, bootstraping continues to use all of my CPUs instead of the -jN jobs from the make command line.
I have tried patching out these lines that remove MAKEFLAGS from the environment for cargo; the MAKEFLAGS value does reach cargo but cargo continues to set up its own jobserver instead.
I can see that removing MAKEFLAGS from the environment was deliberate (as noted in #50629 (comment)), but it would be great if building rustc can cooperate with the rest of the build system by using the same jobserver.
I'm currently working on enhancing the Rust package (currently 1.72.0) in OpenWrt (the build system is based on buildroot). After ensuring the x.py command is prefixed with
+and thatMAKEFLAGSis set correctly, bootstraping continues to use all of my CPUs instead of the-jNjobs from the make command line.I have tried patching out these lines that remove
MAKEFLAGSfrom the environment for cargo; theMAKEFLAGSvalue does reach cargo but cargo continues to set up its own jobserver instead.I can see that removing
MAKEFLAGSfrom the environment was deliberate (as noted in #50629 (comment)), but it would be great if building rustc can cooperate with the rest of the build system by using the same jobserver.