From owner-freebsd-hackers Fri Aug 23 17:19:31 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA28273 for hackers-outgoing; Fri, 23 Aug 1996 17:19:31 -0700 (PDT) Received: from eel.dataplex.net (EEL.DATAPLEX.NET [199.183.109.245]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA28253 for ; Fri, 23 Aug 1996 17:19:27 -0700 (PDT) Received: from [199.183.109.242] (cod [199.183.109.242]) by eel.dataplex.net (8.6.11/8.6.9) with SMTP id TAA04073; Fri, 23 Aug 1996 19:19:18 -0500 X-Sender: rkw@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 23 Aug 1996 19:19:19 -0500 To: Julian Elischer From: rkw@dataplex.net (Richard Wackerbarth) Subject: Re: Am I wrong or is this just stupid?r Cc: hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Julian Elischer writes: >maybe we should have a way of marking when the tools have changed, >in which case an extra pass of Make bootstrap or similar >could fix it.. This is the common method of using "cookies" to represent a portion of the build process. We would probably want to have 3 conditions. 1) Unconditionally build the tools 2) Test to see if the tools are up-to-date 3) Assume the tools are up-to-date as of the time of the cookie. This can be done with two tokens, "tools_built" and "tools_changed". At the top level, "make" tests a rules that says that "tools_built" depends on "tools_changed". The depend rules for "tools_changed" actually forces those tools to get made. To force the tools to be made, remove "tools_built".