From owner-freebsd-stable Tue Apr 23 19:27:10 2002 Delivered-To: freebsd-stable@freebsd.org Received: from smtp-send.myrealbox.com (smtp-send.myrealbox.com [192.108.102.143]) by hub.freebsd.org (Postfix) with ESMTP id 9EF6537B41C for ; Tue, 23 Apr 2002 19:27:05 -0700 (PDT) Received: from jud@smtp-send.myrealbox.com [63.214.219.20] by smtp-send.myrealbox.com with Novell NIMS $Revision: 2.88.1.1 $ on Novell NetWare via secured & encrypted transport (TLS); Tue, 23 Apr 2002 20:26:50 -0600 Date: Tue, 23 Apr 2002 22:26:05 -0400 From: Jud To: freebsd-stable@FreeBSD.ORG Cc: tony@crosswinds.net, kstewart@owt.com, eperrin@beanfield.com Subject: Re: Break in installworld, cvsup'ed today Message-Id: <20020423222605.668886c6.jud@myrealbox.com> X-Mailer: Sylpheed version 0.7.0 (GTK+ 1.2.10; i386--freebsd4.5) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On +Apr 23, Kent Stewart wrote: > > > The only time I have seen a failure like this something went wrong in > the buildworld because something wasn't created. I don't think tr is > supposed to be needed in an installworld. Did your cvsup include > games? Yes, actually as per another response, I specified the full path to tr in the Makefile (gross hack) and other problems occurred. It seems the PATH was getting whacked in several places - things like tr, expr, ex and mkdir (/bin and /usr/bin) are not being found. After a while, I just gave up on specifying full paths. This system is a fresh 4.5R install, with cvsup to 4.5S. I'm just outta ideas (and lack of sleep doesn't help much) -- Tony Holmes _ _ _ _ _ _ _ _ _ _ _ Very much a shot in the dark, but did you try the steps in the order currently specified in the Handbook, including adjkerntz -i? It just happened to me when I tried to 'make world' on Saturday (going from 4.5-RELEASE to -STABLE as you're trying to do) that I errored out for the first time ever. Googling found suggestions that while things installworld needed had in fact been built, installworld wasn't seeing them because they'd taken place in the system's "future." (I hope you understand that better than I think I just explained it.:) Anyhow, if you haven't already, try following the current Handbook instructions to the letter and see if that helps - worked for me. Jud To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message