From owner-freebsd-stable Mon Sep 6 3: 8: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 0C58D14DA0 for ; Mon, 6 Sep 1999 03:08:00 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 11NvgQ-0006fm-00; Mon, 06 Sep 1999 12:07:30 +0200 From: Sheldon Hearn To: "Jeffrey J. Mountin" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: buildword curiousities In-reply-to: Your message of "Mon, 06 Sep 1999 04:52:45 EST." <3.0.3.32.19990906045245.01682400@207.227.119.2> Date: Mon, 06 Sep 1999 12:07:30 +0200 Message-ID: <25653.936612450@axl.noc.iafrica.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 06 Sep 1999 04:52:45 EST, "Jeffrey J. Mountin" wrote: > Only in the past week have gone from just blowing /usr/obj away to doing > that and adding the -DNOCLEAN flag. If it's gone it must be clean. Right? Well as you say, the problem predates your use of NOCLEAN, so what I'm warning against is probably not an issue. Just keep in mind that NOCLEAN implies at least one thing other than "don't worry about what's in my obj tree". Basically, either grep the Makefiles for instances of NOCLEAN and figure out exactly what it does, or don't use it. That's the advice I give people. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message