Bug#320821: Bug#320847: "rubber --pdf" creates a pdf file even if latex failed to compile correctly.
> So I'm tempted to consider this particular bug closed, if that's right with
> you, since it does not really concern rubber.
I agree, I still think the total latex + rubber behaviour is somewhat
strange in this case, but I understand that it is more a peculiarity
than a bug.
> This is really strange, I made rubber return meaningful exit codes a long time
> ago. I would be interested in a minimal example of a source file with errors
> where rubber terminates with exit code 0, this is definitely not supposed to
> happen. I just tried with the case you were talking about, and here is what I
> get (with rubber 1.0 as of Debian testing):
>
> manu ~ > cat foo.tex
> Foo.
> \newpage
> Bar.
> manu ~ > rubber --pdf foo.tex
> compiling foo.tex...
> foo.tex:1: Missing \begin{document}.
> foo.tex:1: leading text: F
> foo.tex:2: The font size command \normalsize is not defined:
> foo.tex:2: leading text: \newpage
> foo.tex:3: Missing \begin{document}.
> foo.tex:3: leading text: B
> foo.tex: compilation aborted: Emergency stop. (job aborted, no legal \end found)
> manu ~ > echo $?
> 1
I must apologize. I tested it again and indeed found that rubber returns
error code 1. I must have made some mistake last time I checked, though
I don't know how. Now I know that rubber returns a good error code I can
easily modify the builder to clean up in case of errors.
So both bugs can be closed IMHO and thanks for all the help/explanation
from both of you.
Greetings,
Bas Kloet
Reply to: