On 30 October 2016 at 17:43, Liviu Ionescu <i...@livius.net> wrote: > >> On 30 Oct 2016, at 10:16, Gavin Smith <gavinsmith0...@gmail.com> wrote: >> >> ... Is etex creating a log file? > > apparently not. > > I tried with the following lines, from the openocd build: > > ilg-mbp:tmp ilg$ mkdir tex > ilg-mbp:tmp ilg$ cd tex > ilg-mbp:tex ilg$ export > PATH=/Users/ilg/Work/no-backup/texlive/install/bin:$PATH > ilg-mbp:tex ilg$ /Users/ilg/opt/homebrew-gae/bin/texi2dvi --pdf --batch -o > openocd.pdf /Users/ilg/Work/openocd/gnuarmeclipse-openocd.git/doc/openocd.texi > /Users/ilg/opt/homebrew-gae/bin/texi2dvi: TeX neither supports -recorder nor > outputs \openout lines in its log file > ilg-mbp:tex ilg$ ls -l > ilg-mbp:tex ilg$ > ilg-mbp:tex ilg$ /Users/ilg/opt/homebrew-gae/bin/texi2dvi --version > texi2dvi (GNU Texinfo 6.3) 7353 > ... > ilg-mbp:tex ilg$ which etex > /Users/ilg/Work/no-backup/texlive/install/bin/etex > ilg-mbp:tex ilg$ etex --version > pdfTeX 3.14159265-2.6-1.40.17 (TeX Live 2016) > kpathsea version 6.2.2 > ... > Compiled with libpng 1.6.21; using libpng 1.6.21 > Compiled with zlib 1.2.8; using zlib 1.2.8 > Compiled with xpdf version 3.04 > ilg-mbp:tex ilg$ > > > the test uses my compiled texlive, the homebrew texinfo, and the openocd tex > file. > > if you can suggest a more relevant test, please let me know and I'll try it.
Maybe $ pdfetex /Users/ilg/Work/openocd/gnuarmeclipse-openocd.git/doc/openocd.texi or $ etex /Users/ilg/Work/openocd/gnuarmeclipse-openocd.git/doc/openocd.texi and see if a log file is created.