On 01/08/2010 02:12 PM, Jean Delvare wrote:
Le vendredi 8 janvier 2010 11:02, Dave Plater a écrit :
On 01/08/2010 11:52 AM, Jean Delvare wrote:
Le vendredi 8 janvier 2010 10:42, Dave Plater a écrit :
I used "%__make %{?jobs:-j%{jobs}} CPU_COUNT=%{jobs} doc" and it works like a charm.
I'm not sure if %{jobs} is guaranteed to be always defined. I suspect not, so the following would probably be safer:
%__make %{?jobs:-j%{jobs} CPU_COUNT=%{jobs}} doc
That being said, this CPU_COUNT= thing looks like a ugly hack and the upstream developers should be invited to get rid of it if possible. Their build process shouldn't depend on how many jobs there are.
The document build consists mostly of ghostscript and tex commands and these jobs are run simultaneously according to the CPU_COUNT= value. It slows everything else down to a crawl on my box but it cuts the build time in half.
Running jobs in parallel is exactly what "make -j" is for. I don't get why they would also need CPU_COUNT=... unless there is a single job which can't be split into individual tasks - but then make -j itself is no longer needed nor desirable.
Anyway, as I don't have the time to dig further into this, I won't comment more on this.
All I can give is the excerpt from INSTALL.txt : Known issues and warnings ......................... The most time consuming task for building the documentation is running LilyPond to build images of music, and there cannot be several simultaneously running `lilypond-book' instances, so `-j' `make' option does not significantly speed up the build process. To help speed it up, the makefile variable CPU_COUNT may be set in `local.make' or on the command line to the number of `.ly' files that LilyPond should process simultaneously, e.g. on a bi-processor or dual core machine make -j3 CPU_COUNT=3 doc The recommended value of CPU_COUNT is one plus the number of cores or processors, but it is advisable to set it to a smaller value if your system has not enough RAM to run that many simultaneous LilyPond instances. Regards Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org