From owner-freebsd-current Fri Nov 10 14:54:04 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA15922 for current-outgoing; Fri, 10 Nov 1995 14:54:04 -0800 Received: from lobster.dataplex.net ([199.183.109.243]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA15883 ; Fri, 10 Nov 1995 14:53:51 -0800 Received: from [199.183.109.242] (COD.DATAPLEX.NET [199.183.109.242]) by lobster.dataplex.net (8.6.11/8.6.9) with SMTP id QAA09525; Fri, 10 Nov 1995 16:53:36 -0600 X-Sender: rkw@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 10 Nov 1995 16:53:37 -0600 To: Terry Lambert From: rkw@dataplex.net (Richard Wackerbarth) Subject: Re: config, other kernel build tools Cc: current@freebsd.org, hackers@freebsd.org Sender: owner-current@freebsd.org Precedence: bulk At 3:44 PM 11/10/95, Terry Lambert wrote: >> At 8:40 PM 11/9/95, Terry Lambert wrote: >> >Like putting them in a "tools" dir at the same level as the kern and >> >compile and arch specific directories. >> >> I certainly have no problem with that location in src/ >> Now I'll throw in the "ringer". gcc and make are also "tools". > >I think I can safely argue that you're not allowed to include them >because they aren't allowed to change as frequently as the config >program. 8-). Frequency of change is NOT the criteria. It is the fact that it might need to change and that it is needed to accomplish a particular compilation of some version of the tree. The generic build files already recognize that you might not want to use the same c compiler all the time. In the same way, you do not wish to use the same config. And in the case of make, Poul is already talking about modifications. There is nothing wrong with that. But the new version of make should not be installed into the running system. It may get there eventually, but in the interim, it belongs in a separate area associated with the build that needs it. ---- Richard Wackerbarth rkw@dataplex.net