On 27 October 2016 at 23:08, Liviu Ionescu <i...@livius.net> wrote: > after some debugging sessions, it looks like texi2dvi expects etex to > generate an output log, or something like this, and if this does not happen, > fails with "TeX neither supports -recorder nor outputs \openout lines in its > log file". > > ... > + tex_cmd='etex --file-line-error </dev/null '\''\nonstopmode'\''' > + batch=false > + tex_cmd='etex --file-line-error </dev/null '\''\nonstopmode'\'' > '\''\input'\'' ./openout.tex' > + verbose '/Users/ilg/opt/homebrew-gae/bin/texi2dvi: running etex > --file-line-error </dev/null '\''\nonstopmode'\'' '\''\input'\'' > ./openout.tex ...' > + false > + rm -fr openout.log > + eval 'etex --file-line-error </dev/null '\''\nonstopmode'\'' '\''\input'\'' > ./openout.tex' > + test -f openout.log <<<<==== file > missing with compiled texinfo > + grep '^\\openout..\? *= *`\?dum\.dum'\''\?' openout.log <<<<==== test > skiped with compiled texinfo > + cd_orig > ... > > any suggestions why this happen?
Is etex creating a log file?
