The ways to specify build parallelization are way to complex and confusing. I propose the following solution: 1) We use --with-num-cpus and --with-max-jobs and --with-sense-load 2) --with-num-cpus defaults to the number of cpus on the machine and is stored in GMAKE_PARALELLISM only 3) --with-max-jobs defaults to the number of cpus divided by two on the machine and is stored in GMAKE_MODULE_PARALELLISM only 4) --with-sense-load defaults to "T" unless using icecream or on windows (where it is "") and is stored in GMAKE_SENSE_LOAD 5) all calls to build.pl are done as: build.pl -P$((${GMAKE_PARALELLISM}/${GMAKE_MODULE_PARALELLISM})) -- -P${GMAKE_MODULE_PARALELLISM} 6) gbuild calls (including tail_build) are done as: make -srj$((${GMAKE_PARALELLISM}*4)) -l$((${GMAKE_PARALELLISM}+1)) when GMAKE_SENSE_LOAD is not empty, or as: make -srj${GMAKE_MODULE_PARALELLISM} otherwise (exception: tail build might use GMAKE_PARALELLISM) The variables @BUILD_NCPUS@ and @BUILD_MAX_JOBS@ will be removed. Configure should warn, if GMAKE_MODULE_PARALELLISM is bigger than GMAKE_PARALELLISM and set it to GMAKE_PARALELLISM.
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Dear bug submitter! Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs. To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem. Yours! Florian
actually has been fixed by Norbert
@Björn: Can you add some rough target info in brackets?
I think we where there by 3.5.X but Im not sure. The release is less relevant here as it is a developer task that was mostly caned about on master.