From: Chris Marusich <cmmarusich@gmail.com>
To: ng0 <contact.ng0@cryptolab.net>
Cc: 26604@debbugs.gnu.org
Subject: bug#26604: documentation: pdf generation is broken
Date: Sat, 22 Apr 2017 21:14:56 -0700 [thread overview]
Message-ID: <87tw5fu5dr.fsf@gmail.com> (raw)
In-Reply-To: <20170422110947.pyepomrq4s3zzntr@abyayala> (ng0's message of "Sat, 22 Apr 2017 11:09:47 +0000")
[-- Attachment #1: Type: text/plain, Size: 713 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-04-23 4: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 [this message]
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
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tw5fu5dr.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=26604@debbugs.gnu.org \
--cc=contact.ng0@cryptolab.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).