From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14286 invoked by alias); 2 Dec 2002 18:23:15 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 14270 invoked from network); 2 Dec 2002 18:23:14 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 2 Dec 2002 18:23:14 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 18Ix6O-0003S8-00; Mon, 02 Dec 2002 14:23:36 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 18IvEI-0004Bb-00; Mon, 02 Dec 2002 13:23:38 -0500 Date: Mon, 02 Dec 2002 10:23:00 -0000 From: Daniel Jacobowitz To: Alexandre Oliva Cc: Nathanael Nerode , gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com, binutils@sources.redhat.com, dj@redhat.com, autoconf@gnu.org Subject: Re: (toplevel) introduce host subdir configuration in Makefile Message-ID: <20021202182338.GA16046@nevyn.them.org> Mail-Followup-To: Alexandre Oliva , Nathanael Nerode , gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com, binutils@sources.redhat.com, dj@redhat.com, autoconf@gnu.org References: <20021128221312.GA20889@doctormoo> <20021202161822.GA11078@nevyn.them.org> <20021202165230.GA12234@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.1i X-SW-Source: 2002-12/txt/msg00028.txt.bz2 On Mon, Dec 02, 2002 at 03:44:21PM -0200, Alexandre Oliva wrote: > One way to try to overcome this limitation in autoconf that has just > occurred to me is to offload the updating of a shared config.cache to > the top-level Makefile. E.g., the Makefile safely copies the > top-level config.cache to a subdirectory before it configures it, and > safely copies it back (or merges it) with the top-level config.cache > when configure finishes. Safety can be accomplished with > > cp ${cache_file} subdir/config.cache > run configure in subdir, with --config-cache=./config.cache > mv subdir/config.cache ${cache_file} > > trying to merge the contents can get trickier, but I believe it can be > done too. > > The one thing we'd have to be careful about is in case the user > specified a config.cache to the top-level, especially /dev/null. We > may have to handle that especially, like autoconf does. Yeah, I think this would be the way to go; but in any case, I suggest that we serialize configure targets if it's practical to do so. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer