Eli Zaretskii writes: > > That's exactly my point: When it cannot produce output due to syntax > > errors in the input, it just gives an error message and exit(1), but > > doesn't remove the existing foobar.o file. > > As Karl explained, makeinfo produces output as a side effect of its > parsing of input, which is different from how GCC works.
I appreciate that Karl is willing to change the implementation of makeinfo in order to match users' desires better. Bruno _______________________________________________ Bug-texinfo mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-texinfo
