From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22763 invoked by alias); 22 Feb 2010 17:48:40 -0000 Received: (qmail 22439 invoked by uid 48); 22 Feb 2010 17:48:28 -0000 Date: Mon, 22 Feb 2010 17:48:00 -0000 Message-ID: <20100222174828.22438.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug other/42980] GCC parallel "make install" failures In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "gary at intrepid dot com" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2010-02/txt/msg02247.txt.bz2 ------- Comment #6 from gary at intrepid dot com 2010-02-22 17:48 ------- Created an attachment (id=19936) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19936&action=view) parallel "make -j6 install" failure logs Attached, a collection of install logs run with SHELL="/bin/sh -x", where the install failed. The first log is for a libgomp install failure, and the rest are for libiberty. Note that it is difficult to reproduce the failures. I found that "make -j6" led to more failures than "make -j" on our system. Also, couldn't get the install-target-libiberty target to fail, but perhaps didn't wait long enough. Instead, ran "make -j6 install". Also, tried running this test on a "ram fs", but couldn't make the installs fail, likely due to different interlocks. Similarly, the installs were more likely to fail on our RAID-ed disk subsystem, populated with high speed drives, than on a file system on a single drive. (These tests were run using the gcc-4.5-20100114 (gcc core) snapshot.) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42980