Eli Zaretskii writes: > makeinfo is not invoked by Make alone. It can (and frequently is) > invoked from the command line.
Also in this case, removing the output file is not useful. A clear error message would do as well. > > For comparison, when gcc compiles a file, "gcc -c foobar.c", it does not > > remove foobar.o when there are syntax errors in foobar.c or one of its > > included files. > > 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. Bruno _______________________________________________ Bug-texinfo mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-texinfo
