[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: problem with texi2dvi from texinfo 6.1

From: Kurt Hornik
Subject: Re: problem with texi2dvi from texinfo 6.1
Date: Tue, 23 Feb 2016 08:14:45 +0100

>>>>> Vincent Belaïche writes:

> Dear Kurt,
> Is the issue that texi2dvi does not make enough runs?


> Could you send also a minimal example of Rd2.tex, I could then make a
> trial on my machine to see if I can reproduce the issue ....

Gavin had also asked for a smaller example (the one I had circulated was
from production use).  

So pls try the following:

Attachment: test1.tex
Description: LaTeX document

For me:

$ texi2dvi test1.tex 
This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015/Debian) 
(preloaded format=latex)
 restricted \write18 enabled.
entering extended mode
LaTeX2e <2016/02/01>
Babel <3.9n> and hyphenation patterns for 79 languages loaded.
(./test1.tex (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
Document Class: article 2014/09/29 v1.4h Standard LaTeX document class

Package hyperref Message: Driver (default): hdvips.

No file test1.aux.

Package hyperref Warning: Rerun to get /PageLabels entry.

[1] [2] (/home/Hornik/tmp/ZZZ/test1.aux)

Package rerunfilecheck Warning: File `test1.out' has changed.
(rerunfilecheck)                Rerun to get outlines right
(rerunfilecheck)                or use package `bookmark'.

LaTeX Warning: Label(s) may have changed. Rerun to get cross-references right.

Output written on test1.dvi (2 pages, 2800 bytes).
Transcript written on test1.log.


$ echo $?


>    Vincent.

> Le 22/02/2016 22:19, Gavin Smith a écrit :
>> The log files you sent help a bit. They contain lines like:
>> Package hyperref Warning: Rerun to get /PageLabels entry.
>> This explains why no "New xref files" messages are being printed by
>> texi2dvi: the function xref_files_changed in texi2dvi sees that text
>> in the log files and doesn't look in the log files. I don't have those
>> lines in my log files (maybe due to different versions of packages),
>> so what happens for me is different.
>> I still don't know where exactly texi2dvi is quitting in your case,
>> alas. Perhaps the output from
>> sh -x ./texi2dvi --verbose Rd2.tex >Rd2.trace
>> could help? I've attached what I got.
>> Also deleting chunks from the file to get a smaller file that gives
>> the same error can only help. (It would make the log files shorter and
>> possibly easier to spot what's wrong.)
>> NB I don't know if the problem is on my end or yours but I have awful
>> trouble reading emails with long logs in the body of the email: could
>> you try sending any long logs or output as attachments instead? That's
>> if you weren't doing that already and my mail reader (GMail web
>> interface) is displaying them inline).

reply via email to

[Prev in Thread] Current Thread [Next in Thread]