On 12.10.06 Nicolas Boulenguez (nicolas.bouleng...@free.fr) wrote:

Hi,

https://bugs.debian.org/392564

> When TeX detects that no output is generated, it does not create or
> overwrite the dvi file. This situation can happen because I use a main
> file and different \include secondary files, while a background job
> runs rubber each second.
> 
> If the old dvi file exists, it stays older than the latex file, and
> rubber compiles eternally. It does not really hurt.
> 
> If no dvi file is present, rubber crashes displaying
> 
<snip>

I simulated your problem by using a tex file generating no dvi file.

hille@sid:~/devel/rubber $ latex 392564.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
(./392564.tex
LaTeX2e <2015/10/01> patch level 1
Babel <3.9m> and hyphenation patterns for 14 languages loaded.
(/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
(./392564.aux) (./392564.aux) )
No pages of output.
Transcript written on 392564.log.

rubber:

hille@sid:~/devel/rubber $ rubber 392564.tex
compiling 392564.tex...
Output file `392564.dvi' was not produced.

Can we assume your problem to be solved?

Hilmar
-- 
sigfault

Attachment: signature.asc
Description: PGP signature

Reply via email to