Re: [PATCH 00/11] Fix PDF doc builds on major distros

From: Vegard Nossum
Date: Sun Aug 17 2025 - 11:33:09 EST


(trimmed Ccs)

Hi Mauro,

Thank you for testing on OL. I'm wondering about some of the results,
however...

On 15/08/2025 13:36, Mauro Carvalho Chehab wrote:
Oracle Linux Server release 9.6:
--------------------------------
PASSED: OS detection: Oracle Linux Server release 9.6
SKIPPED (Sphinx Sphinx 3.4.3): System packages
SKIPPED (Sphinx already installed either as venv or as native package): Sphinx on venv
SKIPPED (Sphinx already installed either as venv or as native package): Sphinx package
PASSED: Clean documentation: Build time: 0:00, return code: 0
PASSED: Build HTML documentation: Build time: 0:06, return code: 0

How is the html PASSED with the build time only 6 seconds, that looks
rather odd to me.

PARTIAL: Build PDF documentation: Test failed (Build time: 0:07, return code: 2)

PDF docs:
---------
PASSED: latex: FAILED (no .tex)

This doesn't seem like it PASSED either if it FAILED.

I tried on OL 9.5 and got:

"""
$ scripts/sphinx-pre-install
...
You should run:

sudo yum install -y ImageMagick graphviz
...
sudo yum install -y python3-sphinx
"""

But I actually need to do this:

sudo yum --enablerepo=ol9_developer_EPEL install -y ImageMagick graphviz

and then

sudo yum --enablrepo=ol9_codeready_builder install -y python3-sphinx

respectively.

After this, I see a bunch of red warnings but 'make htmldocs' succeeds
and after 33 minutes.

For pdfdocs and latexdocs, respectively, I get:

$ make pdfdocs
Documentation/Makefile:156: The 'xelatex' command was not found. Make sure you have it installed and in PATH to produce PDF output.
SKIP Sphinx pdfdocs target.

$ time make latexdocs
make[3]: Nothing to be done for 'latex'.
Using alabaster theme
Using Python kernel-doc
Documentation/i2c/instantiating-devices.rst:36: WARNING: Could not lex literal_block as "dts". Highlighting skipped.

real 21m12.103s
user 20m58.124s
sys 0m18.567s


Vegard