From owner-freebsd-questions Wed Dec 18 7:25:56 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2BB8E37B401 for ; Wed, 18 Dec 2002 07:25:55 -0800 (PST) Received: from otter.mills-atl.com (dsl-64-192-140-77.telocity.com [64.192.140.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id 06C5643EC2 for ; Wed, 18 Dec 2002 07:25:54 -0800 (PST) (envelope-from jmmills@telocity.com) Received: from localhost (jmills@localhost) by otter.mills-atl.com (8.9.3/8.9.3) with ESMTP id KAA02352; Wed, 18 Dec 2002 10:27:46 -0500 X-Authentication-Warning: otter.mills-atl.com: jmills owned process doing -bs Date: Wed, 18 Dec 2002 10:27:46 -0500 (EST) From: John Mills X-Sender: jmills@otter.mills-atl.com Reply-To: John Mills To: JacobRhoden Cc: FreeBSD-questions Subject: Re: buildworld problem on cyrix 166 In-Reply-To: <200212181351.05098.jrhoden@unimelb.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Freebies - In re: the 'ncurses' buildworld failures while upgrading, which I've also experienced: On Wed, 18 Dec 2002, JacobRhoden wrote: > On Wed, 18 Dec 2002 13:23, Ken Kroel wrote: > > i am trying to update an old pc and have run into a problem with the "make > > > CPU: Cyrix 6x86 (486-class CPU) > > Origin = "CyrixInstead" DIR=0x2231 Stepping=2 Revision=2 Perhaps the Cyrix-IBM/166 is the common denominator here, as that is my chip, too. Should I specify the processor to my build environment? I have never tried this. Has it helped others with this build failure? > I had the exact same problem with the exact same machine you appear to have. > This list at the time attributed it to a hardware issue, probably faulty > memory. Try doing a make clean, to clean up everything, and try again. If > the make fails at a different place each time, then its definatly a hardware > problem. I only recall problems from folks doing upgrades (from RELENG_4_5 to RELENG_4_6, _7 in my case). Have others seen the problem when doing 'buildworld' on an installed system at RELENG_4_6 or later, or is this an 'upgrade only' issue? (I have been able to get some partial and redone builds to complete, but never installed them because my purpose is to set a firm foundation under my system and I didn't feel I knew what was in the mix in those cases.) TIA for comments. - John Mills To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message