From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25228 invoked by alias); 5 Jun 2002 16:05:53 -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 25221 invoked from network); 5 Jun 2002 16:05:52 -0000 Received: from unknown (HELO takamaka.int.act-europe.fr) (209.53.17.163) by sources.redhat.com with SMTP; 5 Jun 2002 16:05:52 -0000 Received: by takamaka.int.act-europe.fr (Postfix, from userid 507) id F3D2B89FBA; Wed, 5 Jun 2002 09:05:51 -0700 (PDT) Date: Wed, 05 Jun 2002 09:05:00 -0000 From: Joel Brobecker To: Aidan Skinner Cc: gdb-patches@sources.redhat.com Subject: Re: [PATCH] remove ada-exp.tab.c Message-ID: <20020605090551.A8208@gnat.com> References: <20020604210319.A617@velvet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020604210319.A617@velvet.net>; from aidan@velvet.net on Tue, Jun 04, 2002 at 09:03:19PM +0100 X-SW-Source: 2002-06/txt/msg00075.txt.bz2 > * 2002-06-04 Aidan Skinner > * ada-exp.tab.c: remove, it's a generated file > > (no patch, I'd just cvs remove the file) But if you remove it, you force the dependency on yacc or bison when building GDB, which may not be available on all machines. At ACT, we have taken a different approach where we have this filed checked in our repository, and we regenerate it when we modify ada-exp.y. The same goes for ada-lex.c, generated from ada-lex.l. The situation is analogus to configure and configure.in. -- Joel