From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8689 invoked by alias); 25 Sep 2009 19:31:26 -0000 Received: (qmail 8646 invoked by uid 22791); 25 Sep 2009 19:31:25 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 25 Sep 2009 19:31:23 +0000 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n8PJV9oS018501; Fri, 25 Sep 2009 15:31:09 -0400 Received: from [10.36.8.124] (vpn2-8-124.ams2.redhat.com [10.36.8.124]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id n8PJV1HE017588; Fri, 25 Sep 2009 15:31:03 -0400 Message-ID: <4ABD1A72.8080203@redhat.com> Date: Fri, 25 Sep 2009 19:31:00 -0000 From: Nick Clifton User-Agent: Thunderbird 2.0.0.23 (X11/20090825) MIME-Version: 1.0 To: Ralf Wildenhues , Charles Wilson , Nick Clifton , gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org, binutils@sourceware.org Subject: Re: RFA/RFC: Pass --cache-file=/dev/null on to subconfigures References: <20090925172108.GA1808@gmx.de> In-Reply-To: <20090925172108.GA1808@gmx.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-09/txt/msg00816.txt.bz2 Hi Ralf, > Please do commit it, since I guess it is necessary in practice. Done. > However, this necessity is always a sign of a bug in the GCC/src > build system. True. > Well, with upstream Autoconf, you only ever have one cache file anyway, > so it works there. Really ? I did not realise that. > GCC/src could easily let such a switch cause the > use of different cache file names in the sub-directories. I'm not sure > what the benefit would be, though. Nor do I. It was more of a theoretical situation than anything I might actually expect to happen in real life. Cheers Nick