From owner-freebsd-current Sun Oct 18 14:59:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13435 for freebsd-current-outgoing; Sun, 18 Oct 1998 14:59:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nomad.dataplex.net (nomad.dataplex.net [208.2.87.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13423 for ; Sun, 18 Oct 1998 14:59:28 -0700 (PDT) (envelope-from rkw@nomad.dataplex.net) Received: (from rkw@localhost) by nomad.dataplex.net (8.9.1/8.9.1) id QAA09697; Sun, 18 Oct 1998 16:59:03 -0500 (CDT) (envelope-from rkw) Message-Id: <199810182159.QAA09697@nomad.dataplex.net> Date: Sun, 18 Oct 1998 16:59:03 -0500 (CDT) From: User & Subject: Re: Never ending 'make clean' in kde port? To: tlambert@primenet.com cc: current@FreeBSD.ORG In-Reply-To: <199810182110.OAA11047@usr07.primenet.com> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18 Oct, Terry Lambert wrote: > Which is throwing out the baby with the bathwater. > > The correct thing to do is to explicitly specify dependencies. I agree. One major problem with the present tree is that they are missing many of the dependencies. (They assume that target ordering will somehow make up for it. Witness the problems with SMP and make -j8) > > For things like second order effects, it's important to build using > the headers in the source tree, and not the installed headers, This is also true for the the target builds. However, we need to recognize that a single source tree may be used for multiple purposes. Although one approach would be to clone selected portions of the tree in order to build the cross-compilation tools, that should not be necessary. We should be able to reference the installed headers/library and the sources in the tree to build the bootstrapping tools. However, this is a degression from the original point.with respect to "recursive makes" > The lack of explicit dependencies in the source tree is the true > source of the observed chaos. With explicit dependencies, we get the observed problem. Only by merging the inter-module dependencies can we avoid the repeated "makes" in the prerequisite modules. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message