From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: configure.in: Look for flex
Date: Fri, 17 Jun 2005 09:53:35 +1000 [thread overview]
Message-ID: <87u0jxoo3k.fsf@zip.com.au> (raw)
In-Reply-To: <871x7220ry.fsf@laas.fr> (Ludovic Courtès's message of "Thu, 16 Jun 2005 09:56:01 +0200")
ludovic.courtes@laas.fr (Ludovic Courtès) writes:
>
> Since flex is needed when building from CVS and not needed when building
> from a distribution, what about something like the following:
I think AM_PROG_LEX probably does everything you need, with no
explicit warning code needed. It looks like it sets up the "missing"
script to give a warning in those cases where lex is wanted.
> Then this means that the error message would only be triggered for
> people who passed the `--enable-maintainer-mode' option to `configure'
> (which /should/ be the case for people building from CVS, but I'm not
> sure this is actually the case since I didn't even use it myself ;-)).
If the generated file is checked into the cvs and the dates are right
then you won't need flex for a maintainer build, unless you actually
change the source.
(Maintainer-mode is mostly about regenerating configure, Makefile.in,
etc when the inputs change.)
> BTW, why is the flex-generated file included in the distribution?
Reducing dependencies (see "Releases" in the gnu standards manual),
apparently.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-06-16 23:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 11:47 configure.in: Look for flex Ludovic Courtès
2005-06-15 21:40 ` Kevin Ryde
2005-06-15 22:28 ` Rob Browning
2005-06-15 23:21 ` Kevin Ryde
2005-06-16 7:56 ` Ludovic Courtès
2005-06-16 23:53 ` Kevin Ryde [this message]
2005-06-17 7:19 ` Ludovic Courtès
2005-09-04 23:16 ` Marius Vollmer
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87u0jxoo3k.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-devel@gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).