------- Comment #4 from gary at intrepid dot com 2010-02-08 23:11 -------
Created an attachment (id=19827)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19827&action=view)
Log excerpts of parallel make install failures
Excerpts from parallel install (ie, "make -j6 install") failures. Each file is
separated by "=== <file> ===" strings. Search for the word "cannot" to find
the point of failure. These are mainly libiberty failures, with a single
libssp failure. We saw a similar libgomp failure to the libssp failure, but
apparently didn't save the log file. The problem can be replicated by creating
a loop that repeatedly runs "make -j6 install", and that saves the log when a
failure is detected. The -j6 is arbitrary - this turns out to be the "sweet
spot" for parallel makes on our 4 core system.
Something like this:
#!/bin/sh
dest=`pwd`/rls
for i in `seq 1 1000`; do
for j in 6; do
echo "$i: make -j$j install"
rm -rf $dest
logfile="install-${i}-${j}.log"
make -j$j -C bld DESTDIR=$dest install >& $logfile
if [ $? -ne 0 ]; then
echo "$i: make -j$j install failed."
else
rm -f $logfile
fi
done
done
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42980
