AC_PROG_LEX really checks for the existence of "lex" when "flex" is
not found, so there is no need for AC_PROG_LEX_STRICT.
Furthermore, flex/lex is not really needed for building GHC, so we
issue only a warning instead of dying when flex and lex are not found.
# LocalWords: fi
-dnl
-dnl acspecific.m4's defn of AC_PROG_LEX is a bit too permissive, as it
-dnl defaults to 'lex' if 'flex' isn't found (without checking whether
-dnl 'lex' is actually present along the user's PATH).
-dnl
-AC_DEFUN(AC_PROG_LEX_STRICT,
-[AC_CHECK_PROG(LEX, flex, flex)
-if test -z "$LEX"
-then
- AC_CHECK_PROG(LEX,lex,lex)
- test -z "$LEX" && AC_MSG_ERROR(['lex' or 'flex' is required to compile GHC.])
-fi
-])
dnl
dnl Check to see whether CC (gcc) supports a particular option.
dnl ** Find find command (for Win32's benefit)
FPTOOLS_FIND_FIND
-dnl ** Find lex command (lex or flex) - *doesn't* use autoconf's
-dnl AC_PROG_LEX, since it doesn't actually check whether 'lex'
-dnl exists if 'flex' doesn't.
-AC_PROG_LEX_STRICT
+dnl ** Find lex command (flex or lex)
+AC_PROG_LEX
+test -z "$LEX" && AC_MSG_WARN(['flex' or 'lex' not found])
dnl ** figure out how to do a BSD-ish install
AC_PROG_INSTALL