Re: [Bug-gnulib] AC_PROG_YACC
Derek Robert Price <[email protected]>
| Newsgroups | gmane.comp.sysutils.autoconf.bugs,gmane.comp.version-control.cvs.bugs,gmane.comp.lib.gnulib.bugs |
|---|---|
| Organization | Ximbiot <http://ximbiot.com> |
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Derek Robert Price wrote:
> >>I'd say, since option '-d' is not appropriate in all cases, it's a
>
> >mistake
>
> >>to use it by default. The bug is therefore in the BSD make.
>
> >I'm afraid I agree with you. It might still make sense to have an
> >autoconf workaround for the bug, when detected, however.
>
> I still agree with you but I still think a workaround in macros is
> appropriate, both GNULIB & Autoconf. My new solution just AC_ARG_VARs
> both YACC & YFLAGS, as CC, CFLAGS, CPPFLAGS, etc. are AC_ARG_VARed by
> other autoconf macros and require the user override them as arguments
> to configure or make. Nobody seems to have a problem with autoconf
> doing that for CC, CFLAGS, CPPFLAGS, etc.
>
> Revision 3 of patch for GNULIB attached. I think similar AC_ARG_VAR
> statements for YACC & YFLAGS for AC_PROG_YACC would also be appropriate.
Incidentally, I choose to do this in a macro rather than in the
Makefile.am because Automake warned about the YFLAGS= line interfering
with user variables when I tried. The macro solution also appears to
be consistent with other Autoconf behavior with regards to compilers
and compiler flags.
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
iD8DBQFAloljLD1OTBfyMaQRAtXyAKDpcoshPbY2ZmBn5PT7gMrfwiQ3bgCguRt+
gSPvIDpWlWZO5Ascf/rvxb4=
=TZ7P
-----END PGP SIGNATURE-----