Обсуждение: pdf does not build anymore
Hello,
Today the PDF-build (A4) stopped working (see below
for error).
Are others seeing that too?
I have built this PDF from HEAD almost daily, so
the setup used to be 'good enough'. But perhaps
the slow but steady growth of the manual has reached
some maximum here?
(The "Overfull \hbox"output is not fatal, I just
included it in case it has some info)
Overfull \hbox (1.59999pt too wide) in alignment at lines 232726--233114
[] [] []
[243.0.27
! pdfTeX error (ext4): \pdfendlink ended up in different nesting level than \pd
fstartlink.
<to be read again>
\endgroup \set@typeset@protect
l.233408 ...esult in a run-\/time lookup.\endPar{}
\endNode{}\endDisplayGroup...
! ==> Fatal error occurred, the output PDF file is not finished!
Transcript written on postgres-A4.log.
make: *** [postgres-A4.pdf] Error 1
make: *** Deleting file `postgres-A4.pdf'
rm postgres-A4.tex-pdf
And some extra info which may or may not be useful in debugging this:
Here is how much of TeX's memory you used:
21996 strings out of 246516
173166 string characters out of 1824731
211860 words of memory out of 1000000
24272 multiletter control sequences out of 10000+200000
79955 words of font info for 129 fonts, out of 500000 for 2000
580 hyphenation exceptions out of 1000
28i,12n,43p,307b,1346s stack positions out of 1500i,500n,5000p,200000b,15000s
PDF statistics:
18163 PDF objects out of 300000
10831 named destinations out of 131072
1 words of extra memory for PDF output out of 65536
! ==> Fatal error occurred, the output PDF file is not finished!
Thanks,
Erik Rijkers
On 6/13/13 8:56 AM, Erik Rijkers wrote: > I have built this PDF from HEAD almost daily, so > the setup used to be 'good enough'. But perhaps > the slow but steady growth of the manual has reached > some maximum here? Start bisecting. ;-)
"Erik Rijkers" <er@xs4all.nl> writes: > ! pdfTeX error (ext4): \pdfendlink ended up in different nesting level than \pd > fstartlink. Known failure mode. That happens whenever the text of a <link> phrase crosses a page boundary :-(. We've generally worked around it by tweaking the text so that doesn't happen, but of course we're at risk again the next time anyone adds/changes text in the vicinity. Can you identify what linked phrase is causing the problem? Also, FYI, this is claimed to be fixed in TeX Live 2012: https://bugzilla.redhat.com/show_bug.cgi?id=619481 so a toolchain upgrade is the long-term answer. regards, tom lane
On Thu, Jun 13, 2013 at 3:45 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > "Erik Rijkers" <er@xs4all.nl> writes: >> ! pdfTeX error (ext4): \pdfendlink ended up in different nesting level than \pd >> fstartlink. > > Known failure mode. That happens whenever the text of a <link> phrase > crosses a page boundary :-(. We've generally worked around it by > tweaking the text so that doesn't happen, but of course we're at risk > again the next time anyone adds/changes text in the vicinity. Can you > identify what linked phrase is causing the problem? > > Also, FYI, this is claimed to be fixed in TeX Live 2012: > https://bugzilla.redhat.com/show_bug.cgi?id=619481 > > so a toolchain upgrade is the long-term answer. Just to be clear, it's fixed in all texlive 2012 versions? Or just in the fedora/RH patch? If it's in all of it, then happy enough the official PDF building server (borka) got that toolchain upgrade by default with the upgrade to wheezy a few weeks ago. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/
On Thu, June 13, 2013 15:50, Magnus Hagander wrote: > > If it's in all of it, then happy enough the official PDF building > server (borka) got that toolchain upgrade by default with the upgrade > to wheezy a few weeks ago. > Is there a regularly pre-built 9.3x A4 pdf somewhere? I can only find a html version (of 93devel). Thanks, Erik Rijkers
On Thu, Jun 13, 2013 at 4:13 PM, Erik Rijkers <er@xs4all.nl> wrote: > On Thu, June 13, 2013 15:50, Magnus Hagander wrote: >> >> If it's in all of it, then happy enough the official PDF building >> server (borka) got that toolchain upgrade by default with the upgrade >> to wheezy a few weeks ago. >> > > Is there a regularly pre-built 9.3x A4 pdf somewhere? I can only find a html version (of 93devel). No, at this point they're only built with releases. But there's supposed to be one for the beta I think - but I can't find it myself. Dave - did you not make PDFs for beta1? -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/
Magnus Hagander <magnus@hagander.net> writes: > On Thu, Jun 13, 2013 at 3:45 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> Also, FYI, this is claimed to be fixed in TeX Live 2012: >> https://bugzilla.redhat.com/show_bug.cgi?id=619481 >> so a toolchain upgrade is the long-term answer. > Just to be clear, it's fixed in all texlive 2012 versions? Or just in > the fedora/RH patch? I don't think that Jindrich was claiming he'd fixed the bug himself; I read his comment as just that it'd been fixed by upstream. So it should be in everybody's versions. > If it's in all of it, then happy enough the official PDF building > server (borka) got that toolchain upgrade by default with the upgrade > to wheezy a few weeks ago. Excellent. regards, tom lane
Tom Lane wrote: > Magnus Hagander <magnus@hagander.net> writes: > > On Thu, Jun 13, 2013 at 3:45 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > >> Also, FYI, this is claimed to be fixed in TeX Live 2012: > >> https://bugzilla.redhat.com/show_bug.cgi?id=619481 > >> so a toolchain upgrade is the long-term answer. > > > Just to be clear, it's fixed in all texlive 2012 versions? Or just in > > the fedora/RH patch? > > I don't think that Jindrich was claiming he'd fixed the bug himself; > I read his comment as just that it'd been fixed by upstream. So it > should be in everybody's versions. I just tried on my laptop, which has wheezy and the same toolchain as Borka; it took a few tries because the tex settings need some more adjustments, but it is able to generate the 2960-page PDF. BTW the advice we give about tex settings in our docs is outdated. I first tried with the settings Kris Jurka suggested me years ago: http://www.postgresql.org/message-id/Pine.BSO.4.64.0710081442210.18524@leary.csoft.net but they are not enough; I had to raise pool_size for pdfjadetex even more. Here's what I have that works. Maybe they're not all necessary, but I really have no interest in pruning this. I put this in /etc/texmf/texmf.d/20pgdocs.cnf and re-ran update-texmf: hash_extra.jadetex = 32500 hash_extra.pdfjadetex = 500000 pool_size.jadetex = 500000 pool_size.pdfjadetex = 4000000 string_vacancies.jadetex = 45000 string_vacancies.pdfjadetex = 45000 max_strings.jadetex = 58500 max_strings.pdfjadetex = 500000 pool_free.jadetex = 47500 pool_free.pdfjadetex = 47500 nest_size.jadetex = 500 nest_size.pdfjadetex = 500 param_size.jadetex = 1500 param_size.pdfjadetex = 1500 save_size.jadetex = 5000 save_size.pdfjadetex = 50000 stack_size.jadetex = 1500 stack_size.pdfjadetex = 1500 extra_mem_bot.jadetex = 85000 extra_mem_bot.pdfjadetex = 85000 I also updated borka to have this configuration. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services