* tests/output.at (AT_CHECK_CONFLICTING_OUTPUT): Use
AT_BISON_CHECK_NO_XML rather than AT_BISON_CHECK because an
output file whose name conflicts with a previous output file
is now never generated.
(cherry picked from commit
a3d760ef5d7d9bcab78268f5117c39566aa0345c)
2010-02-22 Joel E. Denny <jdenny@ces.clemson.edu>
+ tests: fix maintainer-xml-check for recent changes.
+ * tests/output.at (AT_CHECK_CONFLICTING_OUTPUT): Use
+ AT_BISON_CHECK_NO_XML rather than AT_BISON_CHECK because an
+ output file whose name conflicts with a previous output file
+ is now never generated.
+
+2010-02-22 Joel E. Denny <jdenny@ces.clemson.edu>
+
portability: fix several issues with M4 subprocess.
M4's output pipe was not being drained upon fatal errors during
]])
[cp ]$1[ expout]
-AT_BISON_CHECK([$3 $1], $5, [], [$4])
+# Because an output file name conflict is still a warning, Bison exits
+# with status 0, so AT_BISON_CHECK does not realize that there may be no
+# output file against which to check the XML. AT_BISON_CHECK_NO_XML
+# avoids that problem.
+AT_BISON_CHECK_NO_XML([$3 $1], $5, [], [$4])
AT_CHECK([[cat $1]], [[0]], [expout])
AT_CLEANUP
])