From owner-freebsd-stable Fri Dec 12 03:06:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA11191 for stable-outgoing; Fri, 12 Dec 1997 03:06:03 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from iworks.InterWorks.org (deischen@iworks.interworks.org [128.255.18.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA11176 for ; Fri, 12 Dec 1997 03:05:59 -0800 (PST) (envelope-from deischen@iworks.InterWorks.org) Received: (from deischen@localhost) by iworks.InterWorks.org (8.7.5/) id FAA24802; Fri, 12 Dec 1997 05:09:49 -0600 (CST) Message-Id: <199712121109.FAA24802@iworks.InterWorks.org> Date: Fri, 12 Dec 1997 05:09:49 -0600 (CST) From: "Daniel M. Eischen" To: Studded@dal.net, asami@vader.cs.berkeley.edu Subject: Re: Build world fails. Cc: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > * I can occasionally get -stable to build with -j n, but it almost > * always fails, and it didn't save me any time. I'd say try it without the > * -j, and see how that does. > > Really? It usually works for me. (Of course, it's only when it works > without -j as well, but the intermittent unbuildability of -stable is > not the issue here.) > > Satoshi I'll grab the latest CTM and try a buildworld without -j. I've done make worlds before on this box and have never had a problem, so I am _reasonably_ sure it's not a hardware problem. Dan Eischen deischen@iworks.InterWorks.org