We don't currently use any, but are about to introduce one. For some more back
story on this, we quote the Bison 3.0 release notes:
*** Use of YACC='bison -y'
TL;DR: With Autoconf <= 2.69, pass -Wno-yacc to (AM_)YFLAGS if you use
Bison extensions.
Traditional Yacc generates 'y.tab.c' whatever the name of the input file.
Therefore Makefiles written for Yacc expect 'y.tab.c' (and possibly
'y.tab.h' and 'y.outout') to be generated from 'foo.y'.
To this end, for ages, AC_PROG_YACC, Autoconf's macro to look for an
implementation of Yacc, was using Bison as 'bison -y'. While it does
ensure compatible output file names, it also enables warnings for
incompatibilities with POSIX Yacc. In other words, 'bison -y' triggers
warnings for Bison extensions.
Autoconf 2.70+ fixes this incompatibility by using YACC='bison -o y.tab.c'
(which also generates 'y.tab.h' and 'y.output' when needed).
Alternatively, disable Yacc warnings by passing '-Wno-yacc' to your Yacc
flags (YFLAGS, or AM_YFLAGS with Automake).
y.tab.c y.tab.h: y.output
y.output: $(top_srcdir)/lib/cgraph/grammar.y
- @YACC@ -dv $(top_srcdir)/lib/cgraph/grammar.y
+ @YACC@ -Wno-yacc -dv $(top_srcdir)/lib/cgraph/grammar.y
cgraph.3.pdf: cgraph.3.ps
@PS2PDF@ $< $@
<TargetMachine>MachineX86</TargetMachine>
</Link>
<PreBuildEvent>
- <Command>win_bison -dy grammar.y -o grammar.c
+ <Command>win_bison -Wno-yacc -dy grammar.y -o grammar.c
win_flex -oscan.c scan.l</Command>
</PreBuildEvent>
</ItemDefinitionGroup>
<TargetMachine>MachineX86</TargetMachine>
</Link>
<PreBuildEvent>
- <Command>win_bison -dy grammar.y -o grammar.c
+ <Command>win_bison -Wno-yacc -dy grammar.y -o grammar.c
win_flex -oscan.c scan.l</Command>
</PreBuildEvent>
</ItemDefinitionGroup>