From owner-freebsd-bugs Wed Aug 16 2:30: 7 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 0A70537BF6A for ; Wed, 16 Aug 2000 02:30:05 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id CAA05147; Wed, 16 Aug 2000 02:30:04 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Wed, 16 Aug 2000 02:30:04 -0700 (PDT) Message-Id: <200008160930.CAA05147@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Sheldon Hearn Subject: Re: gnu/20608: Problem by 'make world' from update 4.0-Release to 4.1-STABLE Reply-To: Sheldon Hearn Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR gnu/20608; it has been noted by GNATS. From: Sheldon Hearn To: "Sascha Valckenier Kips" Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: gnu/20608: Problem by 'make world' from update 4.0-Release to 4.1-STABLE Date: Wed, 16 Aug 2000 10:52:50 +0200 On Wed, 16 Aug 2000 10:50:21 +0200, Sheldon Hearn wrote: > I assume this because this isn't a common problem, and other folks seem > to be managing this upgrade without a hitch. I may be wrong, but if I > were in your shoes, I should check this possibility first. Bleh, I wasn't finished. Other things that I was going to suggest were: 1) Pay careful attention to the output of cvsup -L 2 and confirm that there are no warnings. 2) Delete the source file you're dying on (if it's always the same source file). 3) Blow away your obj tree and clean up the src tree: rm -rf /usr/obj cd /usr/src make cleandir This advice is only useful if your problem is not hardware related. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message