From owner-freebsd-current Fri Dec 18 19:33:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA15354 for freebsd-current-outgoing; Fri, 18 Dec 1998 19:33:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from salmon.hei.net (salmon.hei.net [209.222.163.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA15349 for ; Fri, 18 Dec 1998 19:33:23 -0800 (PST) (envelope-from john@salmon.hei.net) Received: from localhost (john@localhost) by salmon.hei.net (8.8.8/8.8.5) with SMTP id TAA24727; Fri, 18 Dec 1998 19:32:53 -0800 (PST) Date: Fri, 18 Dec 1998 19:32:53 -0800 (PST) From: "John A. Hengstler" To: Alfred Perlstein cc: freebsd-current@FreeBSD.ORG Subject: Re: Buildworld fails In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Normally I would agree with this, except, 2.2.8 make buildworlds and installworlds, work fine on same machine.. On Fri, 18 Dec 1998, Alfred Perlstein wrote: > On Fri, 18 Dec 1998, John Hengstler wrote: > > > Greetings, > > > > I did full install of 3.0-RELEASE onto a spare box. Installed and boot > > perfect with GENERIC. S > > > > So I installed current version of cvsup and have have been slurping updates > > on everything withno problems. > > > > When I go to do a make buildworld. It has been bombing everytime. Here is > > the output of the last try: > > > .... > > cc -fpic -DPIC -O -pipe -Wall -I/usr/obj/elf/usr/src/tmp/usr/include -c > > /usr/src/lib/libtacplus/taclib.c -o taclib.so > > cc: Internal compiler error: program cc1 got fatal signal 11 > > *** Error code 1 > > > > Stop. > > *** Error code 1 > > > .... > > I did do a make update this morning (around 10am pst) before I did this > > buildworld. Other buildworlds have had similiar results. Late last > > night I did build a new kernel no problem thinking that GENERIC was bad. > > Same results as prior times. > > > > Any suggestions? > > > > John Hengstler > > > > Unless this happens in the same spot every time you have a hardware > problem. Aren't there about 10 FAQs out there at least that explain this? > > Try swapping ram, disabling cache, swapping boards. Something has gone > rotten in your box. > > Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com > -- There are operating systems, and then there's FreeBSD. > -- http://www.freebsd.org/ 3.0-current > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message