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. -- Jean Delvare Suse L3 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org