From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14292 invoked by alias); 6 Jan 2003 00:04:53 -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 14285 invoked from network); 6 Jan 2003 00:04:52 -0000 Received: from unknown (HELO main.gmane.org) (80.91.224.249) by 209.249.29.67 with SMTP; 6 Jan 2003 00:04:52 -0000 Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 18VKjz-0005KM-00 for ; Mon, 06 Jan 2003 01:03:39 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gdb-patches@sources.redhat.com Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 18VKjx-0005K9-00 for ; Mon, 06 Jan 2003 01:03:37 +0100 Path: not-for-mail From: Ben Elliston Subject: Re: (toplevel) Fix dramatic breakage for ordinary crosses (related to program_transform_name) Date: Mon, 06 Jan 2003 00:04:00 -0000 Organization: Red Hat Asia-Pacific Pty Ltd Message-ID: References: <200212282057.gBSKva103446@duracef.shout.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@main.gmane.org User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Honest Recruiter) Cache-Post-Path: scooby.brisbane.redhat.com!unknown@scooby.brisbane.redhat.com X-Cache: nntpcache 3.0.1 (see http://www.nntpcache.org/) Cache-Post-Path: webdevap.brisbane.redhat.com!unknown@scooby.brisbane.redhat.com X-Cache: nntpcache 3.0.1 (see http://www.nntpcache.org/) Cc: binutils@sources.redhat.com,gcc-patches@gcc.gnu.org X-SW-Source: 2003-01/txt/msg00193.txt.bz2 >>>>> "Michael" == Michael Elizabeth Chastain writes: Michael> I would also prefer no locks, because I don't want to deal Michael> with locking mechanism headaches when a user with, say, an Michael> SMP Irix NFS client and an HP/UX NFS server has funny build Michael> problems. I have been pondering this problem. It's a shame Autoconf just can't be fixed (and patches even backported to 2.13, if necessary) to change the structure of the cache. These locking problems exist because the cache values are kept in a single file and to control access via a single lock would be too coarse grained. If, instead, the cache were a "dot" directory that contained files whose filenames had the form "key=value", then test results could be examined or updated using atomic file system operations and there should be no races. Michael> So I'm in favor of a dumb, simple, and reliable mechanism Michael> to serialize the configures. I think the performance of large configure runs is becoming too poor to take this line for much longer. Ben