Message-ID: <3990f1c5-2108-44fe-913f-97ae3bb1ff42@gmail.com>
Date: Wed, 20 Aug 2025 20:41:05 +0900
From: Akira Yokosawa <akiyks@...il.com>
To: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
Cc: Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org,
 linux-kernel@...r.kernel.org, Akira Yokosawa <akiyks@...il.com>
Subject: Re: [PATCH 00/11] Fix PDF doc builds on major distros

Hi,

On Wed, 20 Aug 2025 09:15:30 +0200, Mauro Carvalho Chehab wrote:
> Em Wed, 20 Aug 2025 08:54:52 +0900
> Akira Yokosawa <akiyks@...il.com> escreveu:
> 
>> On Tue, 19 Aug 2025 15:32:00 +0200, Mauro Carvalho Chehab wrote:

[...]

>> I've just built a container "FROM ubuntu:plucky", which has inkscape
>> instead of imagemagick + rsvg-convert.
> 
> I don't think that inkscape x imagemagick/rsvg-convert itself has
> anyhting to do with the problems I detected, as they're related to
> font issues (still, I got an issue on one of my builds on kfigure
> write file: encoding is missing at open, which may cause errors).

OK, so you have spent a lot of time to paper over the ImageMagick issue
used as an SVG --> PDF converter.

I have simply given up using ImageMagick and been using inkscape instead.

I can reliably reproduce the warnings and build errors (see below) without
inkscape installed, instead with imagemagick + rsvg-convert installed,
under a ubuntu:plucky based container.

When I run: "make cleandocs; make SPHINXDIRS=gpu latexdocs",
    
     [**NOTE**] SPHINXDIRS=peci is not affected by this issue!

kfigure.py emits warnings like this:

-----------------------------------------------------------------------------------
WARNING: Error #1 when calling: /usr/bin/convert /linux/Documentation/gpu/amdgpu/pipe_and_queue_abstraction.svg /linux/Documentation/output/gpu/latex/pipe_and_queue_abstraction.pdf
WARNING: Warning msg from convert(1): convert: unrecognized color `context-stroke' @ warning/color.c/GetColorCompliance/1064.
convert: non-conforming drawing primitive definition `fill' @ error/draw.c/RenderMVGContent/4548.
-----------------------------------------------------------------------------------

Nevertheless, "make SPHINXDIRS=gpu pdfdocs" continues building gpu.pdf,
but ends up in this error in the middle of xelatex run.

-----------------------------------------------------------------------------------
------------
Run number 1 of rule 'xelatex'
------------
------------
Running 'xelatex --no-pdf -interaction=batchmode -no-shell-escape -no-pdf -recorder  "gpu.tex"'
------------
This is XeTeX, Version 3.141592653-2.6-0.999996 (TeX Live 2025/dev/Debian) (preloaded format=xelatex)
entering extended mode
Latexmk: Getting log file 'gpu.log'
Latexmk: Examining 'gpu.fls'
Latexmk: Examining 'gpu.log'
Latexmk: Index file 'gpu.idx' was written
Latexmk: References changed.
Latexmk: Missing input file 'gpu.toc' (or dependence on it) from following:
  No file gpu.toc.
Latexmk: Missing input file 'gpu.ind' (or dependence on it) from following:
  No file gpu.ind.
Latexmk: References changed.
Latexmk: References changed.
Latexmk: Log file says output to 'gpu.xdv'
Have index file 'gpu.idx', gpu.ind gpu
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 'gpu.log' and/or above output for details

Latexmk: Sometimes, the -f option can be used to get latexmk
  to try to force complete processing.
  But normally, you will need to correct the file(s) that caused the
  error, and then rerun latexmk.
  In some cases, it is best to clean out generated files before rerunning
  latexmk after you've corrected the files.
make[3]: *** [Makefile:29: gpu.pdf] Error 12
make[2]: *** [Documentation/Makefile:148: pdfdocs] Error 1
make[1]: *** [/linux/Makefile:1806: pdfdocs] Error 2
make: *** [Makefile:248: __sub-make] Error 2
-----------------------------------------------------------------------------------

I think this is (mostly) the same as the issue you have been trying hard
to track down.

Lastly, I'm afraid but I have to tell you that I see the same error on my
test branch which has both of your series applied.

>From "./scripts/sphinx-build-wrapper pdfdocs --sphinxdirs gpu":

-----------------------------------------------------------------------------------
------------
Run number 1 of rule 'xelatex'
------------
------------
Running 'xelatex --no-pdf  -no-pdf -interaction=batchmode -no-shell-escape -recorder  "/linux/Documentation/output/gpu/latex/gpu.tex"'
------------
This is XeTeX, Version 3.141592653-2.6-0.999996 (TeX Live 2025/dev/Debian) (preloaded format=xelatex)
entering extended mode
Latexmk: Getting log file 'gpu.log'
Latexmk: Examining 'gpu.fls'
Latexmk: Examining 'gpu.log'
Latexmk: Index file 'gpu.idx' was written
Latexmk: References changed.
Latexmk: Missing input file 'gpu.toc' (or dependence on it) from following:
  No file gpu.toc.
Latexmk: Missing input file 'gpu.ind' (or dependence on it) from following:
  No file gpu.ind.
Latexmk: References changed.
Latexmk: References changed.
Latexmk: Log file says output to 'gpu.xdv'
Have index file 'gpu.idx', gpu.ind gpu
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 'gpu.log' and/or above output for details

Latexmk: Sometimes, the -f option can be used to get latexmk
  to try to force complete processing.
  But normally, you will need to correct the file(s) that caused the
  error, and then rerun latexmk.
  In some cases, it is best to clean out generated files before rerunning
  latexmk after you've corrected the files.

Summary
=======
gpu: FAILED

PDF build failed: not all PDF files were created.
-----------------------------------------------------------------------------------

Please test yourself with SPHINXDIRS=gpu and see what happens under your
test environment.

Thanks,
Akira

Powered by blists - more mailing lists