|author||Guy Harris <email@example.com>||2010-12-25 08:21:53 +0000|
|committer||Guy Harris <firstname.lastname@example.org>||2010-12-25 08:21:53 +0000|
Add a comment asking where to check for YACC/Bison and Flex.
svn path=/trunk/; revision=35262
Diffstat (limited to 'configure.in')
1 files changed, 19 insertions, 0 deletions
diff --git a/configure.in b/configure.in
index 7bf29570da..890a9ca89b 100644
@@ -38,6 +38,25 @@ AC_DEFUN([AC_PROVIDE_AC_LIBTOOL_DLOPEN], )
+# XXX - should autogen.sh check for YACC/Bison and Flex? A user building
+# from a distribution tarball shouldn't have to have YACC/Bison or Flex,
+# as the tarball should contain the results of running YACC/Bison on .y
+# files and running Flex on .l files, but a user building from SVN
+# will have to run YACC/Bison and Flex to process those files.
+# On the other hand, what about users who use a distribution tarball to
+# do development? They *shouldn't* - that's what the SVN repository is
+# for - but they might. They'd get errors if they modify a .y or .l
+# file and try to do a build - but the error should tell them that they
+# need to get YACC/Bison and/or Flex.
+# Then again, getting them shouldn't be too big of a burden.
+# XXX - is the same true of pod2man and pod2html, or are they needed
+# even when building from a distribution tarball?
if test "x$YACCDUMMY" = x