From owner-freebsd-bugs  Tue Apr  7 16:30:06 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA18215
          for freebsd-bugs-outgoing; Tue, 7 Apr 1998 16:30:06 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA18203;
          Tue, 7 Apr 1998 16:30:04 -0700 (PDT)
          (envelope-from gnats)
Date: Tue, 7 Apr 1998 16:30:04 -0700 (PDT)
Message-Id: <199804072330.QAA18203@hub.freebsd.org>
To: freebsd-bugs
Cc: 
From: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
Subject: Re: gnu/6244: Lots of parse errors with gcc in 2.2.6-RELEASE
Reply-To: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR gnu/6244; it has been noted by GNATS.

From: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
To: dmm125@bellatlantic.net
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: gnu/6244: Lots of parse errors with gcc in 2.2.6-RELEASE
Date: Wed, 8 Apr 1998 09:25:45 +1000 (EST)

 You wouldn't be overclocking your CPU, by any chance?
 Failing make world with parse errors is a sure indication of CPU 
 overheating, or faulty RAM.
 
 Danny
 
 /*  Daniel O'Callaghan                                                     */
 /*  HiLink Internet <http://www.hilink.com.au/>       danny@hilink.com.au  */
 /*  FreeBSD - works hard, plays hard...                 danny@freebsd.org  */
 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message