From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31019 invoked by alias); 15 Feb 2011 04:06:42 -0000 Received: (qmail 31007 invoked by uid 22791); 15 Feb 2011 04:06:41 -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, 15 Feb 2011 04:06:35 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 979462BAC41; Mon, 14 Feb 2011 23:06:33 -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 T4N33GyhtS+4; Mon, 14 Feb 2011 23:06:33 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 23D892BAC3E; Mon, 14 Feb 2011 23:06:33 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 2D4251457E4; Tue, 15 Feb 2011 08:06:27 +0400 (RET) Date: Tue, 15 Feb 2011 06:46:00 -0000 From: Joel Brobecker To: Tom Tromey Cc: Pedro Alves , gdb-patches@sourceware.org, Yao Qi Subject: Re: Change gdb/common/ to use Automake Message-ID: <20110215040627.GY2384@adacore.com> References: <4D30E23F.3080103@codesourcery.com> <201102141822.12309.pedro@codesourcery.com> <201102142003.26224.pedro@codesourcery.com> 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-02/txt/msg00314.txt.bz2 > First, we would want to check in generated files, to make it easy to > check out and build gdb. This means that anybody modifying the source > file will need to use the correct version of Automake, to avoid churn in > the repository. I don't think that this is going to be a problem at all. We're familiar with checking in files generated by autoheader, autoconf, etc, and since we've been using gnulib, we've added aclocal (I'm not even sure that I covered them all! :-)). > Second, the output of the tool is fairly opaque. So, when something > goes wrong, you have another layer of goo to wade through. I'm really in that category - having trouble going through the goo. But it's true that we touch these files relatively seldomly, so if it helps in other areas, we can give it a try and see how it goes. It could be a good way to evaluate it for gdbserver, for instance. -- Joel