From: Jonathan Corbet <corbet@lwn.net>
To: Jim Davis <jim.epost@gmail.com>
Cc: linux-doc <linux-doc@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: make pdfdocs fails with v4.9-rc3
Date: Mon, 31 Oct 2016 13:15:24 -0600 [thread overview]
Message-ID: <20161031131524.581accdc@lwn.net> (raw)
In-Reply-To: <CA+r1Zhgj7os_npcj4CbNY4fh4jBC2deVfQB41g-4E+z05H7YAQ@mail.gmail.com>
On Mon, 31 Oct 2016 11:51:20 -0700
Jim Davis <jim.epost@gmail.com> wrote:
> Running make pdfdocs on a Ubuntu 16.04 system fails with
>
> Makefile:58: recipe for target 'media.pdf' failed
> make[2]: *** [media.pdf] Error 1
> Documentation/Makefile.sphinx:79: recipe for target 'pdfdocs' failed
> make[1]: *** [pdfdocs] Error 2
> Makefile:1442: recipe for target 'pdfdocs' failed
> make: *** [pdfdocs] Error 2
>
> It's not clear from the voluminous (>5MB) output from make pdfdocs
> exactly which stage is failing, and there are some pdf files produced
> in output/latex.
Hmm, so it does. It comes down to this:
! LaTeX Error: \DUrole undefined.
See the LaTeX manual or LaTeX Companion for explanation.
Type H <return> for immediate help.
...
l.195 \renewcommand*{\DUrole}
[2]{ #2 }
Where the offending command is in Documentation/media/index.rst. Mauro,
got an idea for what's going on there?
jon
next prev parent reply other threads:[~2016-10-31 19:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 18:51 make pdfdocs fails with v4.9-rc3 Jim Davis
2016-10-31 19:15 ` Jonathan Corbet [this message]
2016-10-31 20:17 ` Mauro Carvalho Chehab
2016-10-31 20:58 ` Mauro Carvalho Chehab
2016-10-31 22:04 ` Jim Davis
2016-10-31 22:40 ` Mauro Carvalho Chehab
2016-10-31 22:41 ` Mauro Carvalho Chehab
2016-11-01 4:51 ` Mauro Carvalho Chehab
2016-11-01 22:11 ` Jim Davis
2016-11-01 22:49 ` Mauro Carvalho Chehab
2016-11-02 14:42 ` Markus Heiser
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=20161031131524.581accdc@lwn.net \
--to=corbet@lwn.net \
--cc=jim.epost@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.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.
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 NNTP newsgroup(s).