Re: [bug #43122] texi2dvi does not compile enough times to get toc

[Vincent Belaïche]

Hello,

My answers inserted below.

Le 21/08/2015 13:42, Gavin Smith a écrit :
> On 20 August 2015 at 22:41, Vincent Belaïche <address@hidden> wrote:
>> Hello Gavin,
>>
>> Your email confirms what I thought, my problem is that my log file does
>> not contain any \openout traces while yours have them. Please note that
>> your diff did not work properly probably because my log uses CRLF EOL's
>> and your uses LF.  To make diff work properly, please try:
>>
>>    diff -ab metafont-for-beginners.log{,-VINCENT}
>
> Isn't metafont-for-beginners.log just that log of the final (e)TeX
> run, so if texi2dvi runs it twice, we won't see what happened from the
> first time that caused it to be read the second time?


Yes, you are correct that your metafont-for-beginners.log is after the
second TeX run, but anyway from the DIFF file that you sent in your next
email I could see that you have the \openout traces already after the
first TeX run.

Please note that in my case the compilation was done with pdftex, not
etex, anyway texinfo does not use any of pdftex add-ons, etex is
susfficient. The difference is compiling with etex is faster and makes a
.dvi, not a .pdf.

>

[...]

>>
>> One more thing I cannot understand: why don't the other output files
>> (index files .ky, .cp, etc...) go tot he New xref files list in your
>> case ?
>
> From my reading of the source of texi2dvi, it looks in the filesystem
> to see what files were produced; it doesn't look at what \openout's
> were done.

That is not my undestanding of the texi2dvi source code, if you look at
texi2dvi SVN-6383:

http://svn.savannah.gnu.org/viewvc/trunk/util/texi2dvi?revision=6383&root=texinfo&view=markup

then the function xref_files_changed (line 776) is used to detect
whether a subsequent run is need. This function compares files (line
804) in lists xref_files_orig, and xref_files_new, and these lists are
made up with the function generated_files_get (line 793).

Now, if you look at code of generated_files_get, it greps (line 712) the
log file for openout traces.



>
> I suggest deleting the *.log, *.aux and *.toc files, and simply do
>
> "etex metafont-for-beginners.tex"
>
> then have a look to see if the *.toc file was actually created. This
> should narrow down the cause of the problem.
>
> "tex metafont-for-beginners.tex"
>

Note that the main file is metafont-for-beginners.texi, not
metafont-for-beginners.tex (filename extension is .texi), anyway I use
etex only.

Ok, I tried the following:

  rm metafont-for-beginners.{aux,log,ky,cp,fn,toc,vr}; \
  etex metafont-for-beginners.texi; \
  ls -l metafont-for-beginners.*

The ouput of ls is as follows:

metafont-for-beginners.aux
metafont-for-beginners.cp
metafont-for-beginners.dvi
metafont-for-beginners.fn
metafont-for-beginners.ky
metafont-for-beginners.log
metafont-for-beginners.log-GAVIN
metafont-for-beginners.pg
metafont-for-beginners.tex
metafont-for-beginners.texi
metafont-for-beginners.toc
metafont-for-beginners.tp
metafont-for-beginners.vr

Please note that the .tex and .log-GAVIN files are not prgrammatically
related to metafont-for-beginners.texi: the former is simply the
original file from CTAN by Geoffrey Tobin, and the later is your
(Gavin's) log file which I gathered from the diff trace in your previous
email.

So yes the .toc and the other output files are there, and that does not
suffice for texi2dvi to trigger one more run. As I said the problem is
that MikTeX pdftex does not traces the \openout into the log file.


   Vincent.

> may work as well, although I had errors with texinfo.tex version
> 2014-12-03.16. Version 2015-08-21.13 does work for me. To use a
> particular texinfo.tex version, I copied the file to the directory I
> was running "tex" in.
>
>> I don't know how to proceed...
>>
>> Karl:
>>
>> - do you think that this is a bug of MikTeX?
>> - why index files are overlooked by texi2dvi, ie not in the xref file
>>   list?
>>
>>    Vincent.


---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel 
antivirus Avast.
http://www.avast.com