summaryrefslogtreecommitdiffstats
path: root/configure
diff options
context:
space:
mode:
authorKaz Kylheku <kaz@kylheku.com>2021-03-22 06:44:28 -0700
committerKaz Kylheku <kaz@kylheku.com>2021-03-22 06:44:28 -0700
commitcc966e1590332779e66d067c12ef79291dceafae (patch)
tree74f63bcaf808a1cf8bb3da88c81786916d7a7787 /configure
parentebbc7fb10c1763d81fadb6328e9f9f4b9f833b28 (diff)
downloadtxr-cc966e1590332779e66d067c12ef79291dceafae.tar.gz
txr-cc966e1590332779e66d067c12ef79291dceafae.tar.bz2
txr-cc966e1590332779e66d067c12ef79291dceafae.zip
build: use yacc pattern rule with "y" as stem.
Thanks to a recent discussion in the GNU Make mailing list about some issue related to grouped patterns, I hit upon the realization that the rule y.tab.h y.tab.c: parser.y has a common stem, y, which can be exploited to write a pattern rule. This is only active in maintainer mode; in user mode, the y.tab.h and y.tab.c are separately produced from .shipped files. * Makefile (y.tab.h): Eliminate rule which detects a removed y.tab.h. (y.tab.c): Delete rule, replacing with new rule. (%.tab.c %.tab.h): New pattern rule, which groups the targets together.
Diffstat (limited to 'configure')
0 files changed, 0 insertions, 0 deletions