From: Andrew Cagney <ac131313@cygnus.com>
To: Aidan Skinner <aidan@velvet.net>
Cc: gdb-patches@sources.redhat.com
Subject: LEX vs FLEX; Was: [PATCH] Basic Ada files
Date: Thu, 23 May 2002 19:59:00 -0000 [thread overview]
Message-ID: <3CEDA59A.3080704@cygnus.com> (raw)
In-Reply-To: <20020522172148.A13611@velvet.net>
Aidan,
> -# This is used to rebuild ada-lex.c from ada-lex.l. If the program is
> -# not defined, but ada-lex.c is present, compilation will continue,
> -# possibly with a warning.
> -FLEX = flex
> -
> -ada-lex.c: ada-lex.l
> - @if [ "$(FLEX)" ] && $(FLEX) --version >/dev/null 2>&1; then \
> - echo $(FLEX) -Isit $(srcdir)/ada-lex.l ">" ada-lex.c; \
> - $(FLEX) -Isit $(srcdir)/ada-lex.l > ada-lex.c; \
> - elif [ ! -f ada-lex.c -a ! -f $(srcdir)/ada-lex.c ]; then \
> - echo "ada-lex.c missing and flex not available."; \
> - false; \
> - elif [ ! -f ada-lex.c ]; then \
> - echo "Warning: ada-lex.c older than ada-lex.l and flex not available."; \
> - fi
(I note you're not the author of this) I'm not exactly comfortable with
making FLEX a condition of being able to build GDB - while the above
tries to hide it, the dependency still exists. I guess we'll need to
come back to that later.
Anyway, can you just re-post this patch with a separate ChangeLog and
with the patch against CVS (using `cvs diff -u' or `cvs diff -p').
Andrew
next prev parent reply other threads:[~2002-05-24 2:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-22 11:54 Aidan Skinner
2002-05-23 19:59 ` Andrew Cagney [this message]
2002-05-23 20:01 ` LEX vs FLEX; Was: " Paul Hilfinger
2002-05-23 21:46 ` Andrew Cagney
2002-05-24 12:41 ` Michael Snyder
2002-05-25 11:20 ` Aidan Skinner
2002-05-29 21:56 ` Andrew Cagney
2002-05-31 12:42 ` Aidan Skinner
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=3CEDA59A.3080704@cygnus.com \
--to=ac131313@cygnus.com \
--cc=aidan@velvet.net \
--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