emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Alan E. Davis" <lngndvs@gmail.com>
To: org-mode <emacs-orgmode@gnu.org>
Subject: make doc fails at PDF: "pdftex exited with bad status"
Date: Thu, 17 Oct 2013 09:17:01 -0700	[thread overview]
Message-ID: <CAF-1L2QfvbNO1ntZaSPWgDSXoZGbj93deTv8-78zae+Cc-rUNg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]

On my Archlinux box with up to date texlive, and a newly cloned org-mode
installation, "make doc" fails with the following messages:

Output written on org.pdf (257 pages, 974386 bytes).
Transcript written on org.log.
/usr/bin/texi2dvi: pdftex exited with bad status, quitting.
make[1]: *** [org.pdf] Error 1
make[1]: Leaving directory `/home/doc/WB/Elisp/org-mode.git/doc'
make: *** [pdf] Error 2

This is a recent happening, within approxiately 2 to 3 weeks.  I downgraded
emacs (also relevant to another recent problem), and re-cloned the git
repo.

Should I run text2pdf on org.texi, in the doc/ directory, the pdf file is
generated cleanly.   I assume there is an issue in doc/Makefile.

One suspects this issue may involve a recent update of the texlive packages
on this system.  In doc/Makefile, is a workaround due to a bug in
texi2dvi.  When I deleted the two lines from doc/Makefile, the same issue
seems to exist, but making of org.pdf is skipped, since it already exists:
the failure is for orgguide.pdf, in this case.

I do not understand makefiles well enough to go any further with this.

Alan Davis

[-- Attachment #2: Type: text/html, Size: 1321 bytes --]

             reply	other threads:[~2013-10-17 16:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-17 16:17 Alan E. Davis [this message]
2013-10-17 17:59 ` make doc fails at PDF: "pdftex exited with bad status" Xebar Saram

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://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAF-1L2QfvbNO1ntZaSPWgDSXoZGbj93deTv8-78zae+Cc-rUNg@mail.gmail.com \
    --to=lngndvs@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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/emacs/org-mode.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).