From: ludovic.courtes@laas.fr (Ludovic Courtès)
Subject: configure.in: Look for flex
Date: Wed, 15 Jun 2005 13:47:23 +0200 [thread overview]
Message-ID: <87u0jzj0z8.fsf@laas.fr> (raw)
Hi,
The following change updates `README' and `configure.in' so that they
mention flex.
Thanks,
Ludovic.
2005-06-16 Ludovic Courtès <ludovic.courtes@laas.fr>
* configure.in: Look for `flex'.
* README: Mention flex as a requirement.
Index: README
===================================================================
RCS file: /cvsroot/guile/guile/guile-core/README,v
retrieving revision 1.98
diff -u -B -b -r1.98 README
--- README 8 Mar 2005 00:54:46 -0000 1.98
+++ README 15 Jun 2005 11:40:03 -0000
@@ -61,6 +61,8 @@
libltdl is used for loading extensions at run-time. It is
available from http://www.gnu.org/software/libtool/
+ - flex, a fast lexical analyzer generator, available from
+ http://www.gnu.org/software/flex/
Special Instructions For Some Systems =====================================
Index: configure.in
===================================================================
RCS file: /cvsroot/guile/guile/guile-core/configure.in,v
retrieving revision 1.267
diff -u -B -b -r1.267 configure.in
--- configure.in 5 Jun 2005 18:15:21 -0000 1.267
+++ configure.in 15 Jun 2005 11:40:03 -0000
@@ -77,6 +77,11 @@
AC_CHECK_PROG(have_makeinfo, makeinfo, yes, no)
AM_CONDITIONAL(HAVE_MAKEINFO, test "$have_makeinfo" = yes)
+AC_CHECK_PROG([have_flex], [flex], [yes], [no])
+if test "x$have_flex" = "xno"; then
+ AC_MSG_ERROR([flex not found. See README.])
+fi
+
AM_PATH_LISPDIR
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2005-06-15 11:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 11:47 Ludovic Courtès [this message]
2005-06-15 21:40 ` configure.in: Look for flex 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
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=87u0jzj0z8.fsf@laas.fr \
--to=ludovic.courtes@laas.fr \
/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).