From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11882 invoked by alias); 1 Mar 2011 04:53:24 -0000 Received: (qmail 11866 invoked by uid 22791); 1 Mar 2011 04:53:23 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 01 Mar 2011 04:53:18 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 9EBB92BB0A2; Mon, 28 Feb 2011 23:53:16 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id pQypVHgrEg+u; Mon, 28 Feb 2011 23:53:16 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 3A8112BB09F; Mon, 28 Feb 2011 23:53:16 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 3C713145A56; Tue, 1 Mar 2011 08:53:03 +0400 (RET) Date: Tue, 01 Mar 2011 04:53:00 -0000 From: Joel Brobecker To: Tom Tromey Cc: gdb-patches@sourceware.org Subject: Re: RFC: remove a bunch of testsuite/**/configure scripts Message-ID: <20110301045303.GI30306@adacore.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) 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: 2011-03/txt/msg00016.txt.bz2 > I'd like to go a few step farther and remove both testsuite/configure > and all the Makefile.in's, but the latter at least were recently updated > to make "make clean" work, so I'm a little reluctant to do this. I'm in favor of at least removing the configure script. For the Makefiles (would we keep the master one in gdb/testsuite/?, I'd say yes, at least as a first step), it's a tougher one. I think it depends on what the consequences in terms of funtionality would be. I don't mind losing "make clean" capability in the testsuite area, but that might be problems for those who build in-tree (sacrilege! :-). -- Joel