diff options
| author | Guy Harris <guy@alum.mit.edu> | 2010-12-25 08:21:53 +0000 |
|---|---|---|
| committer | Guy Harris <guy@alum.mit.edu> | 2010-12-25 08:21:53 +0000 |
| commit | e26e9891b5a1dbf4642aff43503678ac2bb72128 (patch) | |
| tree | 821cb99caefd028aa59ba0ced7d383b99bf717f1 | |
| parent | 3be1fe366dfa6b47bdbbe897a36d5cec8ec740f0 (diff) | |
Add a comment asking where to check for YACC/Bison and Flex.
svn path=/trunk/; revision=35262
| -rw-r--r-- | configure.in | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/configure.in b/configure.in index 7bf29570da..890a9ca89b 100644 --- a/configure.in +++ b/configure.in @@ -38,6 +38,25 @@ AC_DEFUN([AC_PROVIDE_AC_LIBTOOL_DLOPEN], ) AC_LIBTOOL_DLOPEN AC_PROG_LIBTOOL AC_PATH_PROG(PERL, perl) +# +# 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? +# +# AC_PROG_YACC AC_PATH_PROG(YACCDUMMY, $YACC) if test "x$YACCDUMMY" = x |