documentation: pdf generation is broken

  • Done
  • quality assurance status badge
Details
8 participants
  • Andreas Enge
  • Chris Marusich
  • ng0
  • Ludovic Courtès
  • Marius Bakke
  • ng0
  • Ricardo Wurmus
  • zimoun
Owner
unassigned
Submitted by
ng0
Severity
normal
N
N
ng0 wrote on 22 Apr 2017 13:09
(address . bug-guix@gnu.org)
20170422110947.pyepomrq4s3zzntr@abyayala
As long as I run guix I was never able to build the documentation
as pdf. What's wrong with it?

[user@abyayala ~/src/guix/guix]$ make doc/guix.pdf
TEXI2PDF doc/guix.pdf
/gnu/store/jz7jq4w8d4czvgnk9as07rrdbcfjjgjj-profile/bin/texi2dvi: pdftex exited with bad status, quitting.
make: *** [Makefile:3591: doc/guix.pdf] Error 1

--
C
C
Chris Marusich wrote on 23 Apr 2017 06:14
(name . ng0)(address . contact.ng0@cryptolab.net)(address . 26604@debbugs.gnu.org)
87tw5fu5dr.fsf@gmail.com
ng0 <contact.ng0@cryptolab.net> writes:

Toggle quote (8 lines)
> As long as I run guix I was never able to build the documentation
> as pdf. What's wrong with it?
>
> [user@abyayala ~/src/guix/guix]$ make doc/guix.pdf
> TEXI2PDF doc/guix.pdf
> /gnu/store/jz7jq4w8d4czvgnk9as07rrdbcfjjgjj-profile/bin/texi2dvi: pdftex exited with bad status, quitting.
> make: *** [Makefile:3591: doc/guix.pdf] Error 1

I looked into this a week or two ago. I think we're waiting for a newer
release of automake? Perhaps John Darrington knows more. See this
email thread, which I found at the time and seems to contain the
relevant information:


--
Chris
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEy/WXVcvn5+/vGD+x3UCaFdgiRp0FAlj8KkAACgkQ3UCaFdgi
Rp1dYA//aF7tvVpKXCJbGouY1piZlocSlgnphduWjmcqmYmAVBtOvhwr+iNPw511
4+3iO9g/HW9TEw4aIelJmkm3yyQuEyr78a0SiSAmREEs5CQ8GEeO3ZAtFABzYLzj
pX1JQ0uJ4rGUHWHdl+eSAfwZQX7YUV8K8uH1F6/PcbUOdPp0j7SKa89cBfpvhPag
MtNqP1xlA3vwo7T2/WY2jNp0gJKIxpaAD0XCY4kKNpelTpn2jNB+ZMC+r6mc2Svv
w8x+hTkqbP5fZNoq8YvB4e1vn4m9B4+qYM3jhJ71Tzw4jz3t7mnsDoXHOmkhZwD4
rRAXi+H5IKrQma5msCTrr/4FyZ3R5yEfMkDvkIHDfbAsRg5yHJwS/hvqKHSuoJow
e7DfgQ6nLnB92a/Qg9SA87CgFBd5ggLhyfgDgBwGxxPQMLm9m/OCVQJFPAoOjT6N
HpTm0T/p6bODasXDxC/4UuYt+t5pmgrMcbkGNKNS28sJglV38ZEO/j0AtOc7x6NQ
0Y7hKOJRKAGevHYst9QAghTHkl7yElm5+exsHHa3lnVnYArNVnx8iKp8GQa4UFf3
EsURtdV13ALSWLUYIT5oq8IkajfJPuEu3gPNvYVlVif2cpTbSIfIvj4Cj6o9GDTY
uO9oF2NWD7E+fVKLuMMJ3zVI3ViNY5d3Q6Tb0tL2pXmgquONAnE=
=VsHm
-----END PGP SIGNATURE-----

N
N
ng0 wrote on 23 Apr 2017 18:15
(name . Chris Marusich)(address . cmmarusich@gmail.com)(address . 26604@debbugs.gnu.org)
20170423161543.y6w7mhp7uezeywjo@abyayala
Chris Marusich transcribed 1.7K bytes:
Toggle quote (20 lines)
> ng0 <contact.ng0@cryptolab.net> writes:
>
> > As long as I run guix I was never able to build the documentation
> > as pdf. What's wrong with it?
> >
> > [user@abyayala ~/src/guix/guix]$ make doc/guix.pdf
> > TEXI2PDF doc/guix.pdf
> > /gnu/store/jz7jq4w8d4czvgnk9as07rrdbcfjjgjj-profile/bin/texi2dvi: pdftex exited with bad status, quitting.
> > make: *** [Makefile:3591: doc/guix.pdf] Error 1
>
> I looked into this a week or two ago. I think we're waiting for a newer
> release of automake? Perhaps John Darrington knows more. See this
> email thread, which I found at the time and seems to contain the
> relevant information:
>
> https://lists.gnu.org/archive/html/guix-devel/2017-02/msg01074.html
>
> --
> Chris

Oh, right… I've seen this scroll by some time ago.
Okay, since there is no associated open bug (at least with the
obvious keywords), I'll leave this bug open and once
the .pdf generates again it can be closed.

--
C
C
Chris Marusich wrote on 23 Apr 2017 20:42
(address . 26604@debbugs.gnu.org)
87mvb7hso2.fsf@gmail.com
ng0@pragmatique.xyz writes:

Toggle quote (26 lines)
> Chris Marusich transcribed 1.7K bytes:
>> ng0 <contact.ng0@cryptolab.net> writes:
>>
>> > As long as I run guix I was never able to build the documentation
>> > as pdf. What's wrong with it?
>> >
>> > [user@abyayala ~/src/guix/guix]$ make doc/guix.pdf
>> > TEXI2PDF doc/guix.pdf
>> > /gnu/store/jz7jq4w8d4czvgnk9as07rrdbcfjjgjj-profile/bin/texi2dvi: pdftex exited with bad status, quitting.
>> > make: *** [Makefile:3591: doc/guix.pdf] Error 1
>>
>> I looked into this a week or two ago. I think we're waiting for a newer
>> release of automake? Perhaps John Darrington knows more. See this
>> email thread, which I found at the time and seems to contain the
>> relevant information:
>>
>> https://lists.gnu.org/archive/html/guix-devel/2017-02/msg01074.html
>>
>> --
>> Chris
>
> Oh, right… I've seen this scroll by some time ago.
> Okay, since there is no associated open bug (at least with the
> obvious keywords), I'll leave this bug open and once
> the .pdf generates again it can be closed.

Sounds good. I guess I should have opened up a bug report myself.
Thank you for doing it!

--
Chris
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEy/WXVcvn5+/vGD+x3UCaFdgiRp0FAlj89Z0ACgkQ3UCaFdgi
Rp1lMg//Q2D/NEfzt9NPqI6ccGss71ezsp9aW2hHDtNdLDmdmYAcUFEJYygLHw6S
wpuPeM90hmDd0vlRv6kbII2ctw7ftJ1X+gtQWPZY/i1qv+Kk2J47xRkJrS4NDZKg
tFic+StnzngnxxDKBPR9sfRPrp5npuSeTxzNgSJjNfecThqJutq1qIB89L4Is4xL
0RIBZdWNKh8jv7LVvFq/BAGBvcxKu48HXERg1e99QaBxnL91Ht7+E0rrXh1e8xQ2
r1VwDMY2j8bA39wvTRFk7lVRr91PZnhjV5ec/98rh56GdXKmNVom4mWwuiB9Vtta
P/9ltcSdPxiVp9/Fqw+YC4rYZhXC7qJTyiQkwp0Ikl4Th2lybIkD0uRYe0mgMzsd
saAGHJf4YpX9flvx7GezO7JvWiowHsuF3+6ZKe5vYPK9o+WHlQNgDoGjbA6nlsxv
zfq962u05k7CR2CYOplbupNQxKi2WTL0Rhjc0spbQmQRudevPTxCmtqa+xraf0N8
Kaodi+l1NXqUbS2xKBauf/TlYhRxt902dqGZrCzxKOvLniwFaNdTQh3tnDd1n2NQ
1zcEYsuZi8gMzHRZDRC7YxjuFsZARQeSc2BhUWmFptX3quIRfm/xBvARKJXt2uY3
JrcyS04GTOHrH2O6Tux5FpmY/L4fNgVrgnwMYcr29V0inIqeQdM=
=/od1
-----END PGP SIGNATURE-----

L
L
Ludovic Courtès wrote on 5 May 2017 20:53
(name . Chris Marusich)(address . cmmarusich@gmail.com)
874lwz2kzo.fsf@gnu.org
Chris Marusich <cmmarusich@gmail.com> skribis:

Toggle quote (13 lines)
> ng0 <contact.ng0@cryptolab.net> writes:
>
>> As long as I run guix I was never able to build the documentation
>> as pdf. What's wrong with it?
>>
>> [user@abyayala ~/src/guix/guix]$ make doc/guix.pdf
>> TEXI2PDF doc/guix.pdf
>> /gnu/store/jz7jq4w8d4czvgnk9as07rrdbcfjjgjj-profile/bin/texi2dvi: pdftex exited with bad status, quitting.
>> make: *** [Makefile:3591: doc/guix.pdf] Error 1
>
> I looked into this a week or two ago. I think we're waiting for a newer
> release of automake?

AFAIK the ‘texinfo.tex’ file that Automake 1.15 installs is good enough,
as shown by

Can you try running “autoreconf -vfi” with Automake 1.15 installed?

FWIW, I have:

Toggle snippet (10 lines)
$ grep def.texinfoversion build-aux/texinfo.tex
\def\texinfoversion{2016-09-18.18}
$ grep def.texinfoversion $(find $(guix build automake) -name texinfo.tex)
\def\texinfoversion{2013-02-01.11}
$ grep def.texinfoversion ~/src/gnulib/build-aux/texinfo.tex
\def\texinfoversion{2017-04-14.11}
$ (cd ~/src/gnulib/ ; git describe)
v0.1-1312-ga87d5e5c6

HTH,
Ludo’.
Z
Z
zimoun wrote on 28 Sep 2020 21:57
(name . Ludovic Courtès)(address . ludo@gnu.org)
87lfgt3c94.fsf@gmail.com
Dear,

On Fri, 05 May 2017 at 20:53, ludo@gnu.org (Ludovic Courtès) wrote:
Toggle quote (20 lines)
> Chris Marusich <cmmarusich@gmail.com> skribis:
>> ng0 <contact.ng0@cryptolab.net> writes:

>>> As long as I run guix I was never able to build the documentation
>>> as pdf. What's wrong with it?
>>>
>>> [user@abyayala ~/src/guix/guix]$ make doc/guix.pdf
>>> TEXI2PDF doc/guix.pdf
>>> /gnu/store/jz7jq4w8d4czvgnk9as07rrdbcfjjgjj-profile/bin/texi2dvi: pdftex
>>> exited with bad status, quitting.
>>> make: *** [Makefile:3591: doc/guix.pdf] Error 1
>>
>> I looked into this a week or two ago. I think we're waiting for a newer
>> release of automake?
>
> AFAIK the ‘texinfo.tex’ file that Automake 1.15 installs is good enough,
> as shown by
> <https://hydra.gnu.org/job/gnu/master/guix-0.12.0-9.25a4.x86_64-linux>
> <https://hydra.gnu.org/build/2017216/log/raw>.

I do not know what I miss but I get this error:

Toggle snippet (25 lines)
$ guix environment -C guix --ad-hoc texlive-base texlive-fonts-ec
[env]$ ./bootstrap && ./configure --localstatedir=/var/ && make
[env]$ make doc/guix.pdf
TEXI2PDF doc/guix.pdf

kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+3/600 --dpi 603 ecrm1095
mktexpk: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1+3/600; nonstopmode; input ecrm1095
This is METAFONT, Version 2.7182818 (TeX Live 2019) (preloaded base=mf)

(/gnu/store/jq35y4na0bciw1i60p9z44aq82dsp5x2-profile/share/texmf-dist/fonts/source/jknappen/ec/ecrm1095.mf (/gnu/store/jq35y4na0bciw1i60p9z44aq82dsp5x2-profile/share/texmf-dist/fonts/source/jknappen/ec/exbase.mf) (/gnu/store/jq35y4na0bciw1i60p9z44aq82dsp5x2-profile/share/texmf-dist/fonts/source/jknappen/ec/ecrm.mf (/gnu/store/jq35y4na0bciw1i60p9z44aq82dsp5x2-profile/share/texmf-dist/fonts/source/jknappen/ec/exroman.mf
Ok (/gnu/store/jq35y4na0bciw1i60p9z44aq82dsp5x2-profile/share/texmf-dist/fonts/source/jknappen/ec/exaccess.mf

[...]

Ok [48] [49] [50] [51] [52] [53] [54] [55] [56] [57]) (/gnu/store/jq35y4na0bciw1i60p9z44aq82dsp5x2-profile/share/texmf-dist/fonts/source/jknappen/ec/exrligtb.mf
Ok) ) ) )
(some charht values had to be adjusted by as much as 0.07599pt)
Font metrics written on ecrm1095.tfm.
Output written on ecrm1095.603gf (256 characters, 55528 bytes).
Transcript written on ecrm1095.log.
mktexpk: /home/simon/src/guix/wk/emacs-vm/doc/guix.t2p/doc!guix.t2d/pdf/build/ecrm1095.603pk: successfully generated.
/gnu/store/jq35y4na0bciw1i60p9z44aq82dsp5x2-profile/bin/texi2dvi: pdftex exited with bad status, quitting.
make: *** [Makefile:4181: doc/guix.pdf] Error 1

And it is a bit cryptic… What am I doing wrong?


All the best,
simon
A
A
Andreas Enge wrote on 28 Sep 2020 23:15
(name . zimoun)(address . zimon.toutoune@gmail.com)
20200928211550.GA16331@jurong
Hello,

On Mon, Sep 28, 2020 at 09:57:43PM +0200, zimoun wrote:
Toggle quote (2 lines)
> [env]$ make doc/guix.pdf

try this instead:
make V=1 pdf
which will print what happens.

I have the monolithic texlive package in my profile and building the pdf
"almost worked":
...
doc/images/coreutils-size-map.png>
!pdfTeX error: /home/andreas/.guix-profile/bin/pdftex (file doc/images/coreutils-graph.png): reading image file failed
==> Fatal error occurred, no output PDF file produced!

It turns out there are a bunch of empty .png files in doc/images/, with
corresponding non-empty .dot files. I deleted them and installed graphviz
into my profile in the hope that "make pdf" would create the missing
.png files, but it does not.

However, the following "almost almost" worked:
- remove the empty .png files and install graphviz
- "make"
- "make pdf"
I obtained the English, German, French and Spanish pdf documentation, but
then a lot of complaints about unicode characters for the Russian
documentation (and "make doc/guix.zh_CN.pdf" also has unicode problems).

Andreas
L
L
Ludovic Courtès wrote on 16 Oct 2020 12:13
(name . Andreas Enge)(address . andreas@enge.fr)
87362e8onb.fsf@gnu.org
Hi,

Andreas Enge <andreas@enge.fr> skribis:

Toggle quote (27 lines)
> On Mon, Sep 28, 2020 at 09:57:43PM +0200, zimoun wrote:
>> [env]$ make doc/guix.pdf
>
> try this instead:
> make V=1 pdf
> which will print what happens.
>
> I have the monolithic texlive package in my profile and building the pdf
> "almost worked":
> ...
> doc/images/coreutils-size-map.png>
> !pdfTeX error: /home/andreas/.guix-profile/bin/pdftex (file doc/images/coreutils-graph.png): reading image file failed
> ==> Fatal error occurred, no output PDF file produced!
>
> It turns out there are a bunch of empty .png files in doc/images/, with
> corresponding non-empty .dot files. I deleted them and installed graphviz
> into my profile in the hope that "make pdf" would create the missing
> .png files, but it does not.
>
> However, the following "almost almost" worked:
> - remove the empty .png files and install graphviz
> - "make"
> - "make pdf"
> I obtained the English, German, French and Spanish pdf documentation, but
> then a lot of complaints about unicode characters for the Russian
> documentation (and "make doc/guix.zh_CN.pdf" also has unicode problems).

Simon, can you close the issue if this is fine on your side as well?

Maybe it’s a matter (as usual…) of choosing the right texlive-* packages.

Thanks,
Ludo’.
Z
Z
zimoun wrote on 16 Oct 2020 13:16
(name . Ludovic Courtès)(address . ludo@gnu.org)
CAJ3okZ2Cy=LBssFueXEhVi9SZyyL+yt5VGnS5KHKFXpjfo2-AA@mail.gmail.com
Hi,

On Fri, 16 Oct 2020 at 12:13, Ludovic Courtès <ludo@gnu.org> wrote:
Toggle quote (9 lines)
> Andreas Enge <andreas@enge.fr> skribis:

> > On Mon, Sep 28, 2020 at 09:57:43PM +0200, zimoun wrote:
> >> [env]$ make doc/guix.pdf
> >
> > try this instead:
> > make V=1 pdf
> > which will print what happens.

Thanks for the tip.


Toggle quote (22 lines)
> > I have the monolithic texlive package in my profile and building the pdf
> > "almost worked":
> > ...
> > doc/images/coreutils-size-map.png>
> > !pdfTeX error: /home/andreas/.guix-profile/bin/pdftex (file doc/images/coreutils-graph.png): reading image file failed
> > ==> Fatal error occurred, no output PDF file produced!
> >
> > It turns out there are a bunch of empty .png files in doc/images/, with
> > corresponding non-empty .dot files. I deleted them and installed graphviz
> > into my profile in the hope that "make pdf" would create the missing
> > .png files, but it does not.
> >
> > However, the following "almost almost" worked:
> > - remove the empty .png files and install graphviz
> > - "make"
> > - "make pdf"
> > I obtained the English, German, French and Spanish pdf documentation, but
> > then a lot of complaints about unicode characters for the Russian
> > documentation (and "make doc/guix.zh_CN.pdf" also has unicode problems).
>
> Simon, can you close the issue if this is fine on your side as well?

Well, it is not satisfactory for me, yet. It is still "almost almost"
and needs some wizardies to work. At least the doc should be updated
and maybe a manifest file with the correct TeX packages. I mean we
have modular texlive and we recommend to use it but we do not use it
for our own infrastructure and then we rely on the BIG texlive
package. Hum?! :-)

Toggle quote (2 lines)
> Maybe it’s a matter (as usual…) of choosing the right texlive-* packages.

They should be documented at least. (How to find them is another story. ;-))


All the best,
simon
R
Z
Z
zimoun wrote on 4 May 2021 10:02
(name . Ricardo Wurmus)(address . rekado@elephly.net)
86wnsfudt9.fsf@gmail.com
Hi Ricardo,

On Mon, 03 May 2021 at 16:06, Ricardo Wurmus <rekado@elephly.net> wrote:

Toggle quote (2 lines)
> Shall we close this now?

Personally, I am still puzzled to build PDFs of the documentation, even
on core-updates, though I have not followed the recent updates on
master. Maybe I am doing wrong but I still get some errors, as reported
in late messages of the thread [1]. Basically, it ends with:

guix environment -C guix --ad-hoc …wizard stuff…
…
make pdf
…wizard stuff…

I should still miss something.



Cheers,
simon
R
R
Ricardo Wurmus wrote on 4 May 2021 12:04
(name . zimoun)(address . zimon.toutoune@gmail.com)
87zgxastl1.fsf@elephly.net
zimoun <zimon.toutoune@gmail.com> writes:

Toggle quote (22 lines)
> Hi Ricardo,
>
> On Mon, 03 May 2021 at 16:06, Ricardo Wurmus
> <rekado@elephly.net> wrote:
>
>> Shall we close this now?
>
> Personally, I am still puzzled to build PDFs of the
> documentation, even
> on core-updates, though I have not followed the recent updates
> on
> master. Maybe I am doing wrong but I still get some errors, as
> reported
> in late messages of the thread [1]. Basically, it ends with:
>
> guix environment -C guix --ad-hoc …wizard stuff…
> …
> make pdf
> …wizard stuff…
>
> I should still miss something.

At least the first “wizard stuff” is merely a list of packages.
There isn’t anything we can do to avoid the selection of packages,
because that stuff is modular by design. We could have an
arbitrary collection of Texlive packages, but I’m sure we can’t
agree on any good set because what exactly is needed depends on
the document.

It’s like creating an arbitrary set of R packages that should work
well for any number of projects.

If the problem is in figuring out what Texlive packages to install
for generating the Guix manual: we can either document that or add
the required packages to the inputs.

If you still get errors relating to fonts or font maps: this has
been fixed on the “master” branch; the texlive-configuration
profile hook didn’t update the font maps.

--
Ricardo
Z
Z
zimoun wrote on 4 May 2021 13:28
(name . Ricardo Wurmus)(address . rekado@elephly.net)
CAJ3okZ1QNs8ZG=BdAmu_AdWiPGkPR=ATULh2A9Y6pC26vX3uUQ@mail.gmail.com
Hi,

On Tue, 4 May 2021 at 12:04, Ricardo Wurmus <rekado@elephly.net> wrote:

Toggle quote (7 lines)
> At least the first “wizard stuff” is merely a list of packages.
> There isn’t anything we can do to avoid the selection of packages,
> because that stuff is modular by design. We could have an
> arbitrary collection of Texlive packages, but I’m sure we can’t
> agree on any good set because what exactly is needed depends on
> the document.

[...]

Toggle quote (4 lines)
> If the problem is in figuring out what Texlive packages to install
> for generating the Guix manual: we can either document that or add
> the required packages to the inputs.

I agree. Maybe via a manifest file?

Toggle quote (4 lines)
> If you still get errors relating to fonts or font maps: this has
> been fixed on the “master” branch; the texlive-configuration
> profile hook didn’t update the font maps.

Cool! I have missed.

Well, let close this old bug. \o/

Cheers,
simon
M
M
Marius Bakke wrote on 23 May 2021 17:17
(address . 26604-done@debbugs.gnu.org)
878s45qy2h.fsf@gnu.org
zimoun <zimon.toutoune@gmail.com> skriver:

Toggle quote (27 lines)
> Hi,
>
> On Tue, 4 May 2021 at 12:04, Ricardo Wurmus <rekado@elephly.net> wrote:
>
>> At least the first “wizard stuff” is merely a list of packages.
>> There isn’t anything we can do to avoid the selection of packages,
>> because that stuff is modular by design. We could have an
>> arbitrary collection of Texlive packages, but I’m sure we can’t
>> agree on any good set because what exactly is needed depends on
>> the document.
>
> [...]
>
>> If the problem is in figuring out what Texlive packages to install
>> for generating the Guix manual: we can either document that or add
>> the required packages to the inputs.
>
> I agree. Maybe via a manifest file?
>
>> If you still get errors relating to fonts or font maps: this has
>> been fixed on the “master” branch; the texlive-configuration
>> profile hook didn’t update the font maps.
>
> Cool! I have missed.
>
> Well, let close this old bug. \o/

Agreed, closing!
-----BEGIN PGP SIGNATURE-----

iIUEARYKAC0WIQRNTknu3zbaMQ2ddzTocYulkRQQdwUCYKpyBg8cbWFyaXVzQGdu
dS5vcmcACgkQ6HGLpZEUEHeGaAEAk2l1GLARQYjv8jh1HuBM1qKjneptWO0gZRxx
DEF5lYsBAJ/u3IbZezTBhFElUmUvqvUMHUuCDUj28eDdj0k9OoQH
=+Jws
-----END PGP SIGNATURE-----

Closed
?