From: Christoph Hellwig <hch@lst.de>
To: Jonathan Corbet <corbet@lwn.net>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: make pdfdocs fails on Debian stable
Date: Mon, 3 Jan 2022 17:30:50 +0100 [thread overview]
Message-ID: <20220103163050.GA3151@lst.de> (raw)
Hi Jon and Mauro,
when trying to do a make pdfdocs on my Debian stable system I can't
get it to complete. The output below is from linux-next, but mainline
is the same.
------------
Running 'xelatex --no-pdf -interaction=batchmode -no-pdf -recorder "RCU.tex"'
------------
This is XeTeX, Version 3.14159265-2.6-0.999992 (TeX Live 2020/Debian) (preloaded format=xelatex)
restricted \write18 enabled.
entering extended mode
Latexmk: Examining 'RCU.log'
=== TeX engine is 'XeTeX'
Latexmk: Index file 'RCU.idx' was written
Latexmk: References changed.
Latexmk: Log file says output to 'RCU.xdv'
Latexmk: Errors, so I did not complete making targets
Collected error summary (may duplicate other messages):
xelatex: Command for 'xelatex' gave return code 1
Refer to 'RCU.log' for details
Latexmk: Use the -f option to force complete processing,
unless error was exceeding maximum runs, or warnings treated as errors.
make[2]: *** [Makefile:29: RCU.pdf] Error 12
make[1]: *** [Documentation/Makefile:115: pdfdocs] Error 2
make: *** [Makefile:1772: pdfdocs] Error 2
next reply other threads:[~2022-01-03 16:30 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 16:30 Christoph Hellwig [this message]
2022-01-03 16:58 ` make pdfdocs fails on Debian stable Mauro Carvalho Chehab
2022-01-03 17:11 ` Christoph Hellwig
2022-01-03 20:58 ` Mauro Carvalho Chehab
2022-01-03 21:01 ` [PATCH 0/1] Detect the need of texlive-ctex Mauro Carvalho Chehab
2022-01-03 21:01 ` [PATCH 1/1] scripts: sphinx-pre-install: add required ctex dependency Mauro Carvalho Chehab
2022-01-03 22:46 ` Jonathan Corbet
2022-01-04 0:04 ` Akira Yokosawa
2022-01-04 1:54 ` Akira Yokosawa
2022-01-04 8:05 ` Mauro Carvalho Chehab
2022-01-04 10:26 ` Akira Yokosawa
2022-01-05 7:48 ` Mauro Carvalho Chehab
2022-01-05 12:09 ` Akira Yokosawa
2022-01-05 21:42 ` Mauro Carvalho Chehab
2022-01-05 22:57 ` Akira Yokosawa
2022-01-06 0:41 ` [PATCH v2] scripts: sphinx-pre-install: Fix ctex support on Debian Mauro Carvalho Chehab
2022-01-06 2:00 ` Akira Yokosawa
[not found] ` <20220106043707.0d40cd11@coco.lan>
2022-01-09 4:09 ` Akira Yokosawa
2022-01-09 6:28 ` Mauro Carvalho Chehab
2022-01-09 7:48 ` Akira Yokosawa
2022-01-06 22:35 ` Jonathan Corbet
2022-01-06 0:42 ` [PATCH 1/1] scripts: sphinx-pre-install: add required ctex dependency Mauro Carvalho Chehab
2022-01-04 2:00 ` Akira Yokosawa
2022-01-04 6:47 ` make pdfdocs fails on Debian stable Christoph Hellwig
2022-01-04 7:32 ` Akira Yokosawa
2022-01-04 7:36 ` Christoph Hellwig
2022-01-04 7:53 ` Akira Yokosawa
2022-01-04 7:56 ` Christoph Hellwig
2022-01-04 8:07 ` Akira Yokosawa
2022-01-04 8:16 ` Christoph Hellwig
2022-01-04 8:44 ` Akira Yokosawa
2022-01-04 9:31 ` Akira Yokosawa
2022-01-04 13:19 ` Christoph Hellwig
2022-01-04 13:46 ` Akira Yokosawa
2022-01-05 1:47 ` Akira Yokosawa
2022-01-05 7:35 ` Christoph Hellwig
2022-01-05 12:03 ` Akira Yokosawa
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=20220103163050.GA3151@lst.de \
--to=hch@lst.de \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.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).