reassign 728069 texlive-latex-base 2013.20140123-1 retitle 728069 pdflatex exits with non-zero status for no apparent reason affects doxygen thank
Hi Paolo, 2013-11-01 Bálint Réczey <[email protected]>: > Hi Paolo, > > 2013/10/31 Paolo Greppi <[email protected]>: >> Package: doxygen >> Version: 1.8.1.2-2 >> >> --- Please enter the report below this line. --- >> >> Point 14 of the doxygen FAQ (see >> http://www.stack.nl/~dimitri/doxygen/manual/faq.html) states: >> >> 14. When running make in the latex dir I get "TeX capacity exceeded". >> Now what? >> You can edit the texmf.cfg file to increase the default values of the >> various buffers and then run "texconfig init". >> >> In your case, you're exhausting strings. and the configuration file has >> a max_strings item set to 500000. The value 495031 you get is after some >> strings were used by TeX itself. > In the reported case I suspect exceeding the capacity is not the cause > of the problem, but rather a result of an infinite loop due to errors. > To debug the problem I set batch mode off in doc/doxygen.cfg.in: > LATEX_BATCHMODE = NO > > This resulted in a very different error: > ... > LaTeX Info: Redefining \ref on input line 108. > LaTeX Info: Redefining \pageref on input line 108. > LaTeX Info: Redefining \nameref on input line 108. > \@outlinefile=\write4 > \openout4 = `refman.out'. > > Package hyperref Info: Option `pageanchor' set `false' on input line 111. > > ! Missing number, treated as zero. > <to be read again> > \let > l.115 \begin{center} > % > ? > ! Emergency stop. > <to be read again> > \let > l.115 \begin{center} > % > End of file on the terminal! > > > Here is how much of TeX's memory you used: > 11853 strings out of 495031 > 163192 string characters out of 6181530 > 239906 words of memory out of 5000000 > 14936 multiletter control sequences out of 15000+600000 > 6139 words of font info for 16 fonts, out of 8000000 for 9000 > 14 hyphenation exceptions out of 8191 > 48i,0n,43p,236b,98s stack positions out of 5000i,500n,10000p,200000b,80000s > ! ==> Fatal error occurred, no output PDF file produced! > > I think this error is created by Doxygen, not by libcaca because this > is at the very beginning of the Latex documentation. > > Moreover the libcaca package rebuilds fine on Wheezy, so I think the > changes in the way Doxygen generates the Latex documentation caused > this regression. I have debugged the issue further and found two problems. One was processing refman.tex before running pdflatex and I have fixed it in libcaca. The other issue was pdflatex not exiting with zero which makes the pdf generation fail in the Makefile Doxygen generated for creating refman.pdf. I worked around the second issue in libcaca and I hereby reassign this bug to texlive-latex-base. The second issue can be observed here: https://buildd.debian.org/status/fetch.php?pkg=libcaca&arch=i386&ver=0.99.beta18-1.1&stamp=1391865359 ... rm -f latex/libcaca.tex latex/libcaca.pdf (cd latex && pdflatex refman ; makeindex refman.idx ; pdflatex refman ; pdflatex refman ; pdflatex refman ; pdflatex refman ; pdflatex refman; echo "pdflatex exit code: $?") This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013/Debian) restricted \write18 enabled. entering extended mode (./refman.tex LaTeX2e <2011/06/27> Babel <3.9h> and hyphenation patterns for 2 languages loaded. This is makeindex, version 2.15 [TeX Live 2013] (kpathsea + Thai support). Scanning input file refman.idx....done (551 entries accepted, 2 rejected). Sorting entries.......done (5274 comparisons). Generating output file refman.ind....done (1087 lines written, 0 warnings). Output written in refman.ind. Transcript written in refman.ilg. ... This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013/Debian) restricted \write18 enabled. entering extended mode (./refman.tex LaTeX2e <2011/06/27> Babel <3.9h> and hyphenation patterns for 2 languages loaded. pdflatex exit code: 1 mv latex/refman.pdf latex/libcaca.pdf touch stamp-latex ... Cheers, Balint -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
