Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Joel Brobecker <brobecker@gnat.com>
Cc: Aidan Skinner <aidan@velvet.net>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] remove ada-exp.tab.c
Date: Wed, 05 Jun 2002 09:33:00 -0000	[thread overview]
Message-ID: <3CFE3D4F.4030607@cygnus.com> (raw)
In-Reply-To: <20020605090551.A8208@gnat.com>

> * 2002-06-04  Aidan Skinner <aidan@velvet.net>
>> 	* 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 release and snapshot processes include steps to generate these 
files.  Hence the dependency only exists for developers using CVS.

> The situation is analogus to configure and configure.in. 

Similar.

Configure needs to be re-generated with the correct autoconf and we want 
everyone running the same script.  If it isn't we'll end up chasing our 
tail looking for host dependant autoconf bugs :-(

For .l and .y files I think they really should be rebuildable with any 
(and not a specific lex/yacc et.al.).

enjoy,
Andrew



  parent reply	other threads:[~2002-06-05 16:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-04 13:03 Aidan Skinner
2002-06-05  9:05 ` Joel Brobecker
2002-06-05  9:20   ` Aidan Skinner
2002-06-05  9:33   ` Andrew Cagney [this message]
2002-06-06  8:49     ` Aidan Skinner
2002-06-06  9:21       ` Andrew Cagney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3CFE3D4F.4030607@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=aidan@velvet.net \
    --cc=brobecker@gnat.com \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox