From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22754 invoked by alias); 16 Feb 2010 11:04:11 -0000 Received: (qmail 22535 invoked by uid 22791); 16 Feb 2010 11:04:10 -0000 X-SWARE-Spam-Status: No, hits=-6.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,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; Tue, 16 Feb 2010 11:04:08 +0000 Received: from int-mx04.intmail.prod.int.phx2.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.17]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o1GB41BR013221 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 16 Feb 2010 06:04:01 -0500 Received: from [10.36.6.251] (vpn1-6-251.ams2.redhat.com [10.36.6.251]) by int-mx04.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id o1GB3wOl015431; Tue, 16 Feb 2010 06:03:59 -0500 Message-ID: <4B7A7B9E.4050606@redhat.com> Date: Tue, 16 Feb 2010 11:04:00 -0000 From: Nick Clifton User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.7) Gecko/20100120 Fedora/3.0.1-1.fc12 Thunderbird/3.0.1 MIME-Version: 1.0 To: Andreas Schwab CC: binutils@sourceware.org, gdb-patches@sourceware.org, gcc-patches@gcc.gnu.org Subject: Re: Remove config.cache files when reconfiguring at top level References: <4B796E1D.7000104@redhat.com> <4B7A6E32.6070307__49868.1737961762$1266314832$gmane$org@redhat.com> In-Reply-To: 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: 2010-02/txt/msg00381.txt.bz2 Hi Andreas, >> Is that OK with you ? > > Why can't you just put the config.cache removal into distclean? That's > what the bug is all about anyway. Because distclean is a Makefile target and the reconfigure deletes the Makefiles, so there are no distclean targets to be run. What used to happens was: 1. User runs configure. Top level files are created but no sub-directories. 2. User runs make. Sub-directories are created. Makefile and config.cache files are created in the sub-directories. 3. User runs configure again, with different flags. The configure script deletes the Makefiles that were created in the sub-directories, but leaves the config.cache files alone. 4. User runs make distclean. There are no Makefiles present in the sub-directories so the config.cache files are left intact. 5. User runs make. The build fails because the values in the config.cache files in the sub-directories no longer match up with the values specified in the reconfigure. My patch made step 3 delete the config.cache files in directories where a Makefile was being deleted so that step 5 would then execute successfully. Cheers Nick