Error compiling document with new poppler in testing

Tromzy · 2017-10-04 10:57:17

Hi,

I use PDFLATEX to compile documentation and this morning, I got errors while compiling. Turned out the errors were gone when downgrading from poppler 0.60.0, poppler-glib 0.60.0 and poppler-qt5 0.60.0 to their version in extra (0.59.0).

Scimmia · 2017-10-04 14:05:58

"errors" doesn't help

Tromzy · 2017-10-04 15:42:21

Sorry. I get this :

./documentation.tex:66:Undefined control sequence \maketitle

./documentation.tex:66:Extra \fi \maketitle

Tromzy · 2017-10-04 15:47:38

I get those errors too with the 0.59.0, but it compiles successfully.

arojas · 2017-10-04 18:16:40

Tromzy wrote:

Turned out the errors were gone when downgrading from poppler 0.60.0, poppler-glib 0.60.0 and poppler-qt5 0.60.0 to their version in extra (0.59.0).

Tromzy wrote:

I get those errors too with the 0.59.0

You're saying one thing and the opposite. Which one is true? Please post the *full* output, those are latex errors which have nothing to do with poppler

Trilby · 2017-10-04 19:21:17

arojas wrote:

those are latex errors which have nothing to do with poppler

I'm guessing the OP is overinterpretting symptoms. Tromzy, please describe the symptoms, not what you suspect as the cause. I'm guessing that you have some workflow (perhaps some gui/ide/etc) for building and viewing latex documents. I'm further guessing that with the new poppler you try to build and (pre)view the document, but the viewer never comes up. Is this true? This could involve poppler as poppler would be used by many pdf viewers.

loqs · 2017-10-04 20:02:59

Possibly related to https://bugs.archlinux.org/task/55867#comment162051 (I only specified the symbol referenced in that bug report but multiple symbols appear to have their names/linkage changed with the poppler 0.60.0-1 build )
Edit:
https://bugs.archlinux.org/task/55871 which may be a duplicate of https://bugs.archlinux.org/task/55867
Edit2:
https://cgit.freedesktop.org/poppler/po … 97940cf046

Last edited by loqs (2017-10-05 00:41:29)

Tromzy · 2017-10-05 07:19:08

OK, I'm not clear at all ; sorry about that !

I write technical documentation in Sphinx, in Eclipse.

I compile it through Ant in Eclipse to LATEX (sphinx-build).

After that, I open the documentation.tex file in Kile, in which I use the "PDFLatex" button to compile the documentation to PDF.

I get the same errors in poppler v 0.59 and 0.60, but the difference is the PDF document does not build on 0.60.

i tried this morning but poppler seems to have been removed from Testing ?

Edit : did not see the links above ; that explains that !

Last edited by Tromzy (2017-10-05 12:02:23)

Revelation60 · 2017-10-05 10:46:50

Perhaps you can share a minimal version of your document that doesn't work?

loqs · 2017-10-05 15:58:40

Was the poppler-0.60.0-1 rebuild abandonned? ( perhaps waiting for upstream to do an soname bump? ) https://git.archlinux.org/svntogit/pack … 33f5ccc887

arojas · 2017-10-05 16:27:34

loqs wrote:

Was the poppler-0.60.0-1 rebuild abandonned? ( perhaps waiting for upstream to do an soname bump? ) https://git.archlinux.org/svntogit/pack … 33f5ccc887

https://lists.freedesktop.org/archives/ … 12617.html

0.60 was removed from testing, so you should do a 'pacman -Syuu' until this is sorted out

Last edited by arojas (2017-10-05 16:29:54)

Tromzy · 2017-10-06 07:41:14

So, poppler 0.60 is in Testing again, and now it builds my document fine. Thanks for your help and time, guys !

cfr · 2017-10-21 04:05:12

Please note that there is a difference between an error and a warning in LaTeX. Unless you've configured it specially, Kile will stop compilation if you get an error, so no PDF will be produced. Warnings are a different matter. Errors should never ignored: if you force compilation, you cannot rely on the output. Warnings, on the other hand, are just that: warnings. Possible problems which may or may not be a problem for you.

What you're reporting looks like errors, although it is hard to tell. If you are forcing compilation anyway, you do so at your peril. Something is seriously wrong with your code and you should fix it, rather than ignoring it.

Last edited by cfr (2017-10-21 04:07:05)

Arch Linux

#1 2017-10-04 10:57:17

Error compiling document with new poppler in testing

#2 2017-10-04 14:05:58

Re: Error compiling document with new poppler in testing

#3 2017-10-04 15:42:21

Re: Error compiling document with new poppler in testing

#4 2017-10-04 15:47:38

Re: Error compiling document with new poppler in testing

#5 2017-10-04 18:16:40

Re: Error compiling document with new poppler in testing

#6 2017-10-04 19:21:17

Re: Error compiling document with new poppler in testing

#7 2017-10-04 20:02:59

Re: Error compiling document with new poppler in testing

#8 2017-10-05 07:19:08

Re: Error compiling document with new poppler in testing

#9 2017-10-05 10:46:50

Re: Error compiling document with new poppler in testing

#10 2017-10-05 15:58:40

Re: Error compiling document with new poppler in testing

#11 2017-10-05 16:27:34

Re: Error compiling document with new poppler in testing

#12 2017-10-06 07:41:14

Re: Error compiling document with new poppler in testing

#13 2017-10-21 04:05:12

Re: Error compiling document with new poppler in testing

Board footer