A year or so ago, building with make -j >1 was advised against due to the potential to produce spurious build failures, etc. Has that changed? The build time savings is attractive, but if there hasn't been any testing, best to stick to -j1 for now?
The only build scripts where I limit NUMJOBS=-j1:
dependencies/avahi-tqt/avahi-tqt.SlackBuild libraries/pytdeextensions/pytdeextensions.SlackBuild tdebindings/tdebindings.SlackBuild
For everything else:
if [ "$NUMJOBS" = "" ]; then NUMJOBS="`grep -c '^processor' /proc/cpuinfo`" NUMJOBS=$(($NUMJOBS + 2)) export NUMJOBS="-j${NUMJOBS}" fi
Darrell
A year or so ago, building with make -j >1 was advised against due to the potential to produce spurious build failures, etc. Has that changed? The build time savings is attractive, but if there hasn't been any testing, best to stick to -j1 for now?
The only build scripts where I limit NUMJOBS=-j1:
dependencies/avahi-tqt/avahi-tqt.SlackBuild libraries/pytdeextensions/pytdeextensions.SlackBuild tdebindings/tdebindings.SlackBuild
For everything else:
if [ "$NUMJOBS" = "" ]; then NUMJOBS="`grep -c '^processor' /proc/cpuinfo`" NUMJOBS=$(($NUMJOBS + 2)) export NUMJOBS="-j${NUMJOBS}" fi
Darrell
The build farm builds everything on 8-core machines with parallel jobs allowed, and I haven't seen any failures.
Tim
On 01/20/2014 03:47 PM, Darrell Anderson wrote:
The only build scripts where I limit NUMJOBS=-j1:
dependencies/avahi-tqt/avahi-tqt.SlackBuild libraries/pytdeextensions/pytdeextensions.SlackBuild tdebindings/tdebindings.SlackBuild
For everything else:
if [ "$NUMJOBS" = "" ]; then NUMJOBS="`grep -c '^processor' /proc/cpuinfo`" NUMJOBS=$(($NUMJOBS + 2)) export NUMJOBS="-j${NUMJOBS}" fi
I saw that. Thanks. Glad to know you have a list. After experiencing sever spurious failures a year or so ago, I have been gunshy about using it. The difference between -j1 and -j4 is phenomenal (haven't tried anything above actual cores)
-
Darrell Anderson -
David C. Rankin -
Timothy Pearson