Re: [Bug-gnulib] AC_PROG_YACC

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bruno Haible wrote:

>Derek Robert Price wrote:
>
>>>>>My workaround will be to just stick a `YFLAGS=' line in my
>>>>>Makefile.am, but I thought you might like the bug report.
>>>>
>>>>So this means, YFLAGS is meant as a variable through which the
user can
>>>>influence the compilation (like CFLAGS, CPPFLAGS, LDFLAGS etc.). By
>>>>setting it to empty, you give the user less freedom.
>>
>>Not true.  I am _defaulting_ it to empty by setting it via configure.
>
>
>That's reasonable, but for this to work as you expect, the default must
>be set from configure.ac or a .m4 macro, not from Makefile.am.


The patch I submitted with the last email did this in m4/bison.m4 from
GNULIB.

>>My new solution just AC_ARG_VARs both YACC & YFLAGS
>
>
>Sounds OK for YFLAGS. However, for YACC it's not what we want because it
>doesn't enforce the requirement that bison is used.


It's as effective as the:

>  : ${YACC='bison -y'}
>  AC_SUBST(YACC)


that GNULIB's m4/bison.m4 is currently using.  I would argue that my
AC_AARG_VAR version is actually more effective for preserving the use
of overrides in subsequent runs of configure.  Also for ducumenting
the possibility of an override.

I would also cite your argument for maintaining flexibility by
allowing user overrides.  The patch I sent also provides a warning via
`./configure --help' that setting the value of YACC to something other
than `bison -y' is likely to cause problems.

Derek

- --
                *8^)

Email: [email protected]

Get CVS support at <http://ximbiot.com>!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFAlpZoLD1OTBfyMaQRAvdBAKCdMC4Z26Fhj3gSR++rqmTkPI9z2QCeI8nD
e+FwVIaPToPIAeOBxyd2wds=
=udwO
-----END PGP SIGNATURE-----