From: Andreas Enge <andreas@enge.fr>
To: zimoun <zimon.toutoune@gmail.com>
Cc: ng0 <contact.ng0@cryptolab.net>, 26604@debbugs.gnu.org
Subject: bug#26604: documentation: pdf generation is broken
Date: Mon, 28 Sep 2020 23:15:50 +0200 [thread overview]
Message-ID: <20200928211550.GA16331@jurong> (raw)
In-Reply-To: <87lfgt3c94.fsf@gmail.com>
Hello,
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).
Andreas
next prev parent reply other threads:[~2020-09-28 21:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-22 11:09 bug#26604: documentation: pdf generation is broken ng0
2017-04-23 4:14 ` Chris Marusich
2017-04-23 16:15 ` ng0
2017-04-23 18:42 ` Chris Marusich
2017-05-05 18:53 ` Ludovic Courtès
2020-09-28 19:57 ` zimoun
2020-09-28 21:15 ` Andreas Enge [this message]
2020-10-16 10:13 ` Ludovic Courtès
2020-10-16 11:16 ` zimoun
2021-05-03 14:06 ` Ricardo Wurmus
2021-05-04 8:02 ` zimoun
2021-05-04 10:04 ` Ricardo Wurmus
2021-05-04 11:28 ` zimoun
2021-05-23 15:17 ` Marius Bakke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200928211550.GA16331@jurong \
--to=andreas@enge.fr \
--cc=26604@debbugs.gnu.org \
--cc=contact.ng0@cryptolab.net \
--cc=zimon.toutoune@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.