From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27755 invoked by alias); 28 Dec 2002 20:57:50 -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 27738 invoked from network); 28 Dec 2002 20:57:49 -0000 Received: from unknown (HELO duracef.shout.net) (204.253.184.12) by 209.249.29.67 with SMTP; 28 Dec 2002 20:57:49 -0000 Received: (from mec@localhost) by duracef.shout.net (8.11.6/8.11.6) id gBSKva103446; Sat, 28 Dec 2002 14:57:36 -0600 Date: Sat, 28 Dec 2002 13:22:00 -0000 From: Michael Elizabeth Chastain Message-Id: <200212282057.gBSKva103446@duracef.shout.net> To: aoliva@redhat.com, dj@delorie.com Subject: Re: (toplevel) Fix dramatic breakage for ordinary crosses (related to program_transform_name) Cc: binutils@sources.redhat.com, drow@mvista.com, gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com X-SW-Source: 2002-12/txt/msg00736.txt.bz2 My two cents: To me, a race is a race. Just don't have them in the first place and no bugs will creep in. I would also prefer no locks, because I don't want to deal with locking mechanism headaches when a user with, say, an SMP Irix NFS client and an HP/UX NFS server has funny build problems. So I'm in favor of a dumb, simple, and reliable mechanism to serialize the configures. Michael C