From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19367 invoked by alias); 23 Dec 2002 20:39:16 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 19352 invoked from network); 23 Dec 2002 20:39:13 -0000 Received: from unknown (HELO mailout6-0.nyroc.rr.com) (24.92.226.125) by 209.249.29.67 with SMTP; 23 Dec 2002 20:39:13 -0000 Received: from doctormoo (syr-24-24-16-193.twcny.rr.com [24.24.16.193]) by mailout6-0.nyroc.rr.com (8.11.6/RoadRunner 1.20) with ESMTP id gBNKd1k00203 for ; Mon, 23 Dec 2002 15:39:01 -0500 (EST) Received: from neroden by doctormoo with local (Exim 3.36 #1 (Debian)) id 18QZKh-0004EL-00 for ; Mon, 23 Dec 2002 15:37:51 -0500 Date: Mon, 23 Dec 2002 13:25:00 -0000 To: gcc@gcc.gnu.org Subject: Re: Serialization dependencies muck up configure-on-demand Message-ID: <20021223203751.GA16255@doctormoo> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i From: Nathanael Nerode X-SW-Source: 2002-12/txt/msg01368.txt.bz2 Daniel mentioned: >However, GNU make has the answer. We'd probably have to autoconf for >this feature, it's quite new: > * A new feature exists: order-only prerequisites. These >prerequisites > affect the order in which targets are built, but they do not >impact > the rebuild/no-rebuild decision of their dependents. That is to >say, > they allow you to require target B be built before target A, >without > requiring that target A will always be rebuilt if target B is >updated. > Patch for this feature provided by Greg McGary . > >The syntax is: >TARGETS : NORMAL-PREREQUISITES | ORDER-ONLY-PREREQUISITES > >So if that works in a test at autoconf time, we could use it. Quite right; if configure detects that this is available, we should use this in the Makefile rather than the existing scheme. Unfortuntately, I'm not feeling up to coding this for a while. :-( Would there be interest in temporarily disabling the serialization dependencies (since .NOTPARALLEL is still there) until we can get a better solution for all this? I'm just thinking of "if (0)"ing them out in 'configure.in' for the time being. --Nathanael