Thread (67 messages) 67 messages, 5 authors, 2025-09-15

Re: [PATCH v4 08/19] tools/docs: sphinx-build-wrapper: add a wrapper for sphinx-build

From: Akira Yokosawa <akiyks@gmail.com>
Date: 2025-09-12 14:03:47
Also in: lkml

On Fri, 12 Sep 2025 13:04:20 +0200, Mauro Carvalho Chehab wrote:
Em Fri, 12 Sep 2025 19:15:44 +0900
Akira Yokosawa [off-list ref] escreveu:
quoted
[-CC: rust people and list]

OK, Looks like I have to bite.

On Wed, 10 Sep 2025 15:33:34 +0200, Mauro Carvalho Chehab wrote:
[...]
quoted
The current approach of using LaTeX for PDF is dirty:

- Sphinx can't produce a LaTeX file from the Kernel trees without
  hundreds of warnings;
- latexmk hides some of them, but even it just one warning is reported,
  the return status is not zero.  
This sounds interesting to me.
As far I remember, I have never seen such strange results of latexmk
under build envs where all the necessary packages are properly installed.
I saw it here on multiple distros including Fedora (which is the one
I use on my desktop). Media jenkins CI running on Debian always suffered
from such issues, up to the point I started ignoring pdf build results.
So please provide exact steps for me to see such errors.

I don't have any issues after strictly following the suggestions from
sphinx-pre-install under Fedora.

I even invoked [...]/output/latex/Makefile manually after running
"make latexdocs" by:

  - cd [...]/output/latex/
  - make PDFLATEX="latexmk -xelatex" LATEXOPTS="-interaction=batchmode -no-shell-escape" -j6 -O all

, and all the PDFs were built without any issues.

Quite puzzling ...

Or does your Fedora have some Noto CJK variable fonts installed?

Hmm ...

Thanks,
Akira
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help