From owner-freebsd-current Sat Apr 13 21:50:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA23171 for current-outgoing; Sat, 13 Apr 1996 21:50:59 -0700 (PDT) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA23165 for ; Sat, 13 Apr 1996 21:50:55 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.7.5/8.6.5) with SMTP id VAA03095; Sat, 13 Apr 1996 21:50:47 -0700 (PDT) Message-Id: <199604140450.VAA03095@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost [127.0.0.1] didn't use HELO protocol To: "Marc G. Fournier" cc: current@freebsd.org Subject: Re: Can someone explain why... In-reply-to: Your message of "Sun, 14 Apr 1996 00:29:21 EDT." From: David Greenman Reply-To: davidg@Root.COM Date: Sat, 13 Apr 1996 21:50:46 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> The only way to troubleshoot this kind of problem is to first look at your >> motherboard settings for correctness and then start replacing components until >> the problem goes away. I would try changing the memory first. >> > Okay, I could probably accept this (and most likely will in the end), >but why would disabling -O allow it to compile, and then if I remove the >object file, re-enable -O cause it to fail exactly the same way? Simple - you have a memory problem and the part of memory that is caching gcc is wrong. It just happens that the code involved is only exercised when you use -O. It's easy to test this: just reboot your computer and see if the problem goes away. If it persists, then you might have a corrupt gcc binary. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project