From: Akira Yokosawa <akiyks@gmail.com>
To: hch@lst.de
Cc: corbet@lwn.net, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, mchehab@kernel.org
Subject: Re: make pdfdocs fails on Debian stable
Date: Tue, 4 Jan 2022 16:32:14 +0900 [thread overview]
Message-ID: <8f21b702-abc2-c9aa-7593-9aff17e61ed1@gmail.com> (raw)
In-Reply-To: <20220104064708.GA15446@lst.de>
Hi Christoph,
On Tue, 4 Jan 2022 07:47:08 +0100, Christoph Hellwig wrote:
> On Mon, Jan 03, 2022 at 09:58:31PM +0100, Mauro Carvalho Chehab wrote:
>> Ah, the error is specific to RCU.tex then?
>
> Yes.
>
>>
>> You'll need to re-run xelatex with -interaction=interactive, in
>> order to be able to identify what's the root cause.
>>
>> You could do this by using LATEXOPTS, e. g.:
>>
>> $ make SPHINXDIRS=RCU LATEXOPTS="-interaction=interactive" pdfdocs
>>
>> With that, LaTeX will stop at the offending line from the .tex file.
>>
>> On a quick test here, I'm getting these at Fedora 35:
>>
>> (/usr/share/texlive/texmf-dist/tex/latex/l3packages/xtemplate/xtemplate.sty)
>>
>> ! LaTeX Error: File `ctexhook.sty' not found.
>>
>> Type X to quit or <RETURN> to proceed,
>> or enter new name. (Default extension: sty)
>>
>> It seems that a recent change (probably to better address issues with
>> Chinese and Japanese translation) added an extra dependency to some
>> stylesheet.
>>
>> I solved it by installing this package: "texlive-ctex".
>
> There is no texlive-ctex on Debian, but ctexhook.sty is installed as
> part of texlive-extra-utils. Here are the last lines from the
> interactive run:
>
> (/usr/share/texlive/texmf-dist/tex/latex/ctex/ctexhook.sty)
> (/usr/share/texlive/texmf-dist/tex/xelatex/xecjk/xeCJK.cfg))
> (/usr/share/texlive/texmf-dist/tex/latex/etoolbox/etoolbox.sty)
> Writing index file RCU.idx
> (./RCU.aux)
> Runaway argument?
> {\contentsline {chapter}{\numberline {16}A Tour Through TREE\_RCU’s\ETC.
> ! File ended while scanning use of \@writefile.
> <inserted text>
> \par
> l.191 \begin{document}
>
> ?
I suspect you are suffering from corrupt RCU.aux (or whatever other
intermediate files xelatex generates).
What happens you run
$ make cleandocs
before
$ make SPHINXDIRS=RCU LATEXOPTS="-interaction=interactive" pdfdocs
?
Thanks, Akira
next prev parent reply other threads:[~2022-01-04 7:32 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 16:30 make pdfdocs fails on Debian stable Christoph Hellwig
2022-01-03 16:58 ` 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 [this message]
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=8f21b702-abc2-c9aa-7593-9aff17e61ed1@gmail.com \
--to=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=hch@lst.de \
--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).