public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "WISD00M at GMX dot NET" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/29049] possible problem: building gcc >= 4.2 on i686 GNU/Linux|SMP (non-64bit) platform fails Date: Wed, 13 Sep 2006 00:44:00 -0000 [thread overview] Message-ID: <20060913004448.16621.qmail@sourceware.org> (raw) In-Reply-To: <bug-29049-13226@http.gcc.gnu.org/bugzilla/> ------- 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
next prev parent reply other threads:[~2006-09-13 0:44 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-09-12 23:48 [Bug other/29049] New: " WISD00M at GMX dot NET 2006-09-12 23:53 ` [Bug other/29049] " WISD00M at GMX dot NET 2006-09-12 23:53 ` pinskia at gcc dot gnu dot org 2006-09-12 23:54 ` WISD00M at GMX dot NET 2006-09-12 23:54 ` WISD00M at GMX dot NET 2006-09-12 23:55 ` WISD00M at GMX dot NET 2006-09-12 23:56 ` WISD00M at GMX dot NET 2006-09-12 23:57 ` WISD00M at GMX dot NET 2006-09-12 23:58 ` WISD00M at GMX dot NET 2006-09-13 0:10 ` WISD00M at GMX dot NET 2006-09-13 0:12 ` WISD00M at GMX dot NET 2006-09-13 0:14 ` WISD00M at GMX dot NET 2006-09-13 0:24 ` WISD00M at GMX dot NET 2006-09-13 0:27 ` pinskia at gcc dot gnu dot org 2006-09-13 0:30 ` WISD00M at GMX dot NET 2006-09-13 0:36 ` WISD00M at GMX dot NET 2006-09-13 0:44 ` WISD00M at GMX dot NET [this message] 2006-09-13 0:51 ` WISD00M at GMX dot NET 2006-09-13 0:57 ` joseph at codesourcery dot com 2006-09-13 1:11 ` WISD00M at GMX dot NET 2006-09-13 1:11 ` WISD00M at GMX dot NET 2006-09-13 1:16 ` WISD00M at GMX dot NET 2006-09-13 2:56 ` hjl at lucon dot org 2006-09-13 3:16 ` WISD00M at GMX dot NET 2006-09-13 3:24 ` WISD00M at GMX dot NET 2006-09-13 5:02 ` WISD00M at GMX dot NET 2006-09-13 5:46 ` hjl at lucon dot org 2006-09-13 6:20 ` WISD00M at GMX dot NET 2006-09-13 15:03 ` hjl at lucon dot org 2006-10-24 8:19 ` pinskia at gcc dot gnu dot org 2007-08-02 1:14 ` lauras at gcc dot gnu dot org 2007-08-02 1:14 ` lauras at gcc dot gnu dot 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=20060913004448.16621.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).