From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24803 invoked by alias); 28 Dec 2002 19:00:04 -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 24744 invoked from network); 28 Dec 2002 19:00:03 -0000 Received: from unknown (HELO delorie.com) (207.22.48.162) by 209.249.29.67 with SMTP; 28 Dec 2002 19:00:03 -0000 Received: from envy.delorie.com (envy.delorie.com [207.22.48.171]) by delorie.com (8.11.6/8.9.1) with ESMTP id gBSIxbW20247; Sat, 28 Dec 2002 13:59:37 -0500 Received: (from dj@localhost) by envy.delorie.com (8.11.6/8.11.2) id gBSIxap07606; Sat, 28 Dec 2002 13:59:36 -0500 Date: Sat, 28 Dec 2002 11:01:00 -0000 Message-Id: <200212281859.gBSIxap07606@envy.delorie.com> X-Authentication-Warning: envy.delorie.com: dj set sender to dj@delorie.com using -f From: DJ Delorie To: drow@mvista.com CC: aoliva@redhat.com, gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com, binutils@sources.redhat.com In-reply-to: <20021228185007.GA22186@nevyn.them.org> (message from Daniel Jacobowitz on Sat, 28 Dec 2002 13:50:07 -0500) Subject: Re: (toplevel) Fix dramatic breakage for ordinary crosses (related to program_transform_name) References: <20021228093127.GA455@doctormoo> <20021228163419.GA10686@nevyn.them.org> <20021228175919.GA17177@nevyn.them.org> <20021228185007.GA22186@nevyn.them.org> X-SW-Source: 2002-12/txt/msg00732.txt.bz2 > Now you're speaking my language. This even lets me say "make > configure-gdb" to configure exactly the directories I need. Sure, some > reconfigures may end up taking place in parallel; I posit that if we > see a config.cache problem then it should be solved by fixing > _autoconf_ to update the cache atomically. Not just update, but *merge*. Autoconf reads the cache, does lots of processing, then writes the cache. The cache may have been updated during the processing, and you don't want to toss those updates. But it would be nice if autoconf managed this problem for us. It would mean migrating to a new version of autoconf, of course.