From owner-freebsd-stable Sat Sep 16 23:25: 4 2000 Delivered-To: freebsd-stable@freebsd.org Received: from shark.harmonic.co.il (jupiter.harmonic.co.il [192.116.140.62]) by hub.freebsd.org (Postfix) with ESMTP id E54F937B423 for ; Sat, 16 Sep 2000 23:24:59 -0700 (PDT) Received: from localhost (roman@localhost) by shark.harmonic.co.il (8.9.3/8.9.3) with ESMTP id JAA13644; Sun, 17 Sep 2000 09:24:47 +0300 Date: Sun, 17 Sep 2000 09:24:47 +0300 (IDT) From: Roman Shterenzon To: Kent Stewart Cc: pahowes@fair-ware.com, freebsd-stable@FreeBSD.ORG Subject: Re: Makeworld is dying... In-Reply-To: <39C42DF4.978A63C@urx.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Perhaps we should add an entry to a FAQ (if it's not already there), describing the problem, and, a good indication of a bad ram or undercooled cpu would be trying buildworld couple of times (without -DNOCLEAN) and watch where it fails. If it fails in different places - then it's almost sure hardware problem, if it fails in the same place, it's still can be a hardware problem, for example some c++ file which demands more memory then others to compile. Can someone add it to FAQ, or shall I fill a PR? :) On Sat, 16 Sep 2000, Kent Stewart wrote: > > > "Paul A. Howes" wrote: > > > > All- > > > > When I attempt a buildworld on a brand new FreeBSD system (IBM/Cyrix-166+, > > 64MB memory, 20GB Maxtor drive), it dies while building the ncurses library. > > This happen whether it's the version of the source code on the 4.1 CD-Rom > > disc, or the latest and greatest 4-STABLE code from a cvsup. Any help would > > be appreciated. The tail of the trace log is included below. > > Signal 11's during a buildworld are usually caused by memory and a few > things such as cpu cooling. I finished a buildworld at 1:30 PDT (about > 2 hours before your message arrived) and I didn't have any problems. > Do you have another 64MB of memory that you could switch as a test of > your memory. > > Kent > > > > > Thanks! > > > > -- > > Paul A. Howes > > pahowes@fair-ware.com > > > > cc -fpic -DPIC -O -pipe -I. -I/usr/src/lib/libncurses - > > /usr/src/lib/libncurses/../../contrib/ncurses/ncurses -I/usr/src/lib/libncur > > ses/../../contrib/ncurses/include -Wall -DFREEBSD_NATIVE -DNDEBUG -DHAVE_CON > > FIG_H -DTERMIOS -I/usr/obj/usr/src/i386/usr/include -c > > /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/alloc_entry.c -o > > alloc_entry.So > > > > cc: Internal compiler error: program cc1 got fatal signal 11 > > *** Error code 1 > > > > Stop in /usr/src/lib/libncurses. > > *** Error code 1 > > > > Stop in /usr/src. > > *** Error code 1 > > > > Stop in /usr/src. > > *** Error code 1 > > > > Stop in /usr/src. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > -- > Kent Stewart > Richland, WA > > mailto:kbstew99@hotmail.com > http://kstewart.urx.com/kstewart/index.html > FreeBSD News http://daily.daemonnews.org/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message