From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23649 invoked by alias); 28 Dec 2002 22:25:10 -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 23635 invoked from network); 28 Dec 2002 22:25:09 -0000 Received: from unknown (HELO lacrosse.corp.redhat.com) (66.187.233.200) by 209.249.29.67 with SMTP; 28 Dec 2002 22:25:09 -0000 Received: from free.redhat.lsd.ic.unicamp.br (aoliva2.cipe.redhat.com [10.0.1.156]) by lacrosse.corp.redhat.com (8.11.6/8.9.3) with ESMTP id gBSMOtY20507; Sat, 28 Dec 2002 17:24:55 -0500 Received: from free.redhat.lsd.ic.unicamp.br (localhost.localdomain [127.0.0.1]) by free.redhat.lsd.ic.unicamp.br (8.12.6/8.12.6) with ESMTP id gBSMOsMK018998; Sat, 28 Dec 2002 20:24:54 -0200 Received: (from aoliva@localhost) by free.redhat.lsd.ic.unicamp.br (8.12.6/8.12.6/Submit) id gBSMOso5018994; Sat, 28 Dec 2002 20:24:54 -0200 To: DJ Delorie Cc: drow@mvista.com, gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com, binutils@sources.redhat.com 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> <200212281859.gBSIxap07606@envy.delorie.com> <200212282151.gBSLp4Z09145@envy.delorie.com> From: Alexandre Oliva Organization: GCC Team, Red Hat Date: Sat, 28 Dec 2002 15:22:00 -0000 In-Reply-To: <200212282151.gBSLp4Z09145@envy.delorie.com> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-12/txt/msg00741.txt.bz2 On Dec 28, 2002, DJ Delorie wrote: >> > But it would be nice if autoconf managed this problem for us. >> >> It can't. Consider that the config.cache file specified in the >> command line may be in a directory that is not writable, > That's a different type of problem. Does autoconf allow for failure > to write to config.cache? It checks whether the file is writable, and then it overwrites the file. Whether the directory is writable doesn't matter. It just makes it harder to choose the location of the lock file. -- Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/ Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org} CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org} Free Software Evangelist Professional serial bug killer