Hi, I fished this in the autoconf m-list, it may interest some of you.
Begin forwarded message: > Date: Wed, 15 Jan 2014 05:12:02 +0100 > From: Alexander Holler <[email protected]> > To: Bob Friesenhahn <[email protected]> > Cc: [email protected] > Subject: Re: parallelized configure [...] >> free software packages are not constructed correctly so that they can >> take advantage of parallel builds. > > Hmm, I'm using the parallel feature from gnu make very successful since > ext4 with support for nanosecond timestamps appeared (so since many > years). Without a fs with high resolution timestamps I had a lot of > problems, but with high resolution timestamps it works most of the time > like a charm. This can explain a good bunch of builds that fail once or twice initially, but if you persist they eventually make it. Myth busted: heisenbuilds? :) I have found *much* improved performance and reliability experience by using /dev/shm, as opposed to other local or shared filesystem, as build dir. The above can be a good explanation of why there is this tendency. cheers, F. ps. spoiler: there is no such thing as parallelized configure -- echo "sysadmin know better bash than english" | sed s/min/mins/ \ | sed 's/better bash/bash better/' # Yelling in a CERN forum
