From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16655 invoked by alias); 13 Sep 2006 00:44:58 -0000 Received: (qmail 16622 invoked by uid 48); 13 Sep 2006 00:44:48 -0000 Date: Wed, 13 Sep 2006 00:44:00 -0000 Message-ID: <20060913004448.16621.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug other/29049] possible problem: building gcc >= 4.2 on i686 GNU/Linux|SMP (non-64bit) platform fails In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "WISD00M at GMX dot NET" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2006-09/txt/msg01124.txt.bz2 List-Id: ------- Comment #16 from WISD00M at GMX dot NET 2006-09-13 00:44 ------- Also, with regards to "bad hardware": this is a multiprocessor server system that's in use every day, it's got numerous inbuilt hardware failure-detection mechanisms, so as soon as there's a CPU, memory or hard disk problem, the admin (me) gets notified immediatley. And there are clearly not any warnings at all. So, given all these self-tests (that even take almost ~5 minutes before the actual system really boots up) I should actually be able to be reasonably sure that this is no hardware problem at all. You said you were able to build it on i686-linux-gnu, was this also an SMP machine? I am really more than willing to take into consideration that this is a local (software) problem (i.e. due to parts of the GNU toolchain being outdated or whatever), nonetheless the previously mentioned google findings suggest that it isn't a totally isolated issue at all. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29049