From owner-freebsd-current Tue Sep 22 20:11:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10076 for freebsd-current-outgoing; Tue, 22 Sep 1998 20:11:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA10059 for ; Tue, 22 Sep 1998 20:11:27 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id UAA09399; Tue, 22 Sep 1998 20:11:16 -0700 (PDT) (envelope-from jdp) Message-Id: <199809230311.UAA09399@austin.polstra.com> To: Harlan.Stenn@pfcs.com Subject: Re: a.out buildworld still failing... In-Reply-To: <18722.906451258@brown.pfcs.com> References: <18722.906451258@brown.pfcs.com> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Tue, 22 Sep 1998 20:11:16 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <18722.906451258@brown.pfcs.com>, Harlan Stenn wrote: > I frequently re-cvsup and start with an *empty* /var/obj, just to be sure. > > This is about as far as I get; the irritating bit is that the failure point > keeps moving around. The disk is local - no NFS. ... > eelf_i386.c:753: parse error before `lang_statemen' > eelf_i386.c:57: warning: `gldelf_i386_find_statement_assignment' declared `stati > c' but never defined You've got some sort of hardware problem or kernel problem. What the compiler is seeing as "lang_statemen" is actually "lang_statement_union_type". It's as though your file is truncated, or filled with a block of 0s at that point. If you failed to mention that you're overclocking, please give yourself 3 firm whacks on the hand with a wooden ruler. :-) John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message