From owner-cvs-all Tue Feb 20 19:32:10 2001 Delivered-To: cvs-all@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 8899837B699; Tue, 20 Feb 2001 19:32:00 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id OAA23983; Wed, 21 Feb 2001 14:31:51 +1100 Date: Wed, 21 Feb 2001 14:31:17 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Warner Losh Cc: Kris Kennaway , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/share/mk sys.mk In-Reply-To: <200102201426.f1KEQWs02309@billy-club.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Feb 2001, Warner Losh wrote: > In message <200102200837.f1K8bpj89576@freefall.freebsd.org> Kris Kennaway writes: > : We now set up the reasonable default for i386 and alpha here -- given this > : it probably makes sense to remove the corresponding code from make(1). > > Probably not. We really do not want to pollute sys.mk with any more > variables than we absolutely have to. It is included for all > Makefiles on the system, not just the ones to build the system. > Adding things there can cause problems elsewhere. But polluting make(1) is almost equivalent to polluting sys.mk. The pollution is just easier to implement and harder to remove in make(1). I have changed my mind a bit about this. MACHINE_CPU is not (yet?) nearly as fundamental as the other MACHINE_* variables. It is currently just a build option for libcrypto, so it could be handled like other build options. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message