From: ludovic.courtes@laas.fr (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: configure.in: Look for flex
Date: Thu, 16 Jun 2005 09:56:01 +0200 [thread overview]
Message-ID: <871x7220ry.fsf@laas.fr> (raw)
In-Reply-To: <87wtov1epk.fsf@zip.com.au> (Kevin Ryde's message of "Thu, 16 Jun 2005 07:40:23 +1000")
Hi,
Kevin Ryde <user42@zip.com.au> writes:
> No, this shouldn't be an error. The dist includes the generated C
> code so you don't need lex in a normal build.
>
> (You need lex if you change the ".l", and in a maintainer build maybe,
> so a configure check is good, but it shouldn't be an error.)
Since flex is needed when building from CVS and not needed when building
from a distribution, what about something like the following:
if test "x$USE_MAINTAINER_MODE" = "xyes"; then
AC_MSG_ERROR([flex not found. See README.])
else
AC_MSG_WARN([flex not found but only needed when building from CVS.])
fi
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 ;-)).
BTW, why is the flex-generated file included in the distribution?
Thanks,
Ludovic.
_______________________________________________
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 7:56 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 [this message]
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=871x7220ry.fsf@laas.fr \
--to=ludovic.courtes@laas.fr \
--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).