public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gary at intrepid dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/42980] GCC parallel "make install" failures Date: Mon, 08 Feb 2010 23:11:00 -0000 [thread overview] Message-ID: <20100208231132.32279.qmail@sourceware.org> (raw) In-Reply-To: <bug-42980-9975@http.gcc.gnu.org/bugzilla/> ------- 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
next prev parent reply other threads:[~2010-02-08 23:11 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-02-05 21:46 [Bug other/42980] New: GCC parllel " gary at intrepid dot com 2010-02-05 22:38 ` [Bug other/42980] " pinskia at gcc dot gnu dot org 2010-02-05 23:03 ` gary at intrepid dot com 2010-02-08 18:18 ` [Bug other/42980] GCC parallel " rwild at gcc dot gnu dot org 2010-02-08 23:11 ` gary at intrepid dot com [this message] 2010-02-21 16:13 ` rwild at gcc dot gnu dot org 2010-02-22 17:48 ` gary at intrepid dot com 2010-02-24 22:15 ` rwild at gcc dot gnu dot org 2010-02-24 22:17 ` rwild at gcc dot gnu dot org 2010-02-24 22:18 ` rwild at gcc dot gnu dot org 2010-02-24 22:22 ` rwild at gcc dot gnu dot org 2010-02-28 9:57 ` rwild at gcc dot gnu dot org 2010-02-28 10:41 ` pluto at agmk dot net 2010-03-02 6:10 ` rwild at gcc dot gnu dot org [not found] <bug-42980-4@http.gcc.gnu.org/bugzilla/> 2011-06-20 16:34 ` hp at gcc dot gnu.org 2011-06-22 21:35 ` rwild at gcc dot gnu.org 2011-06-22 22:19 ` gary at intrepid dot com 2011-11-07 15:08 ` jb at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20100208231132.32279.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).