On Thu, 2 May 2002, Bruno Haible wrote:
> > GCC doesn't produce foobar.o file at all in such cases, IIRC. > > 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. _______________________________________________ Bug-texinfo mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-texinfo
