From: Akira Yokosawa <akiyks@gmail.com>
To: mchehab+huawei@kernel.org
Cc: corbet@lwn.net, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, rdunlap@infradead.org,
Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH 2/2] docs: Makefile: avoid a warning when using without texlive
Date: Sat, 27 Sep 2025 18:12:19 +0900 [thread overview]
Message-ID: <1d993906-bae3-41eb-963f-de960cc56dd0@gmail.com> (raw)
In-Reply-To: <f9ceb569-363c-4806-9451-4a4ef83b38ca@gmail.com>
Sorry, a quick follow-up.
On Sat, 27 Sep 2025 16:35:08 +0900, Akira Yokosawa wrote:
> On Fri, 26 Sep 2025 12:16:19 +0200, Mauro Carvalho Chehab wrote:
>> As reported by Randy, running make htmldocs on a machine
>> without textlive now produce warnings:
>>
>> $ make O=DOCS htmldocs
>> ../Documentation/Makefile:70: warning: overriding recipe for target 'pdfdocs'
>> ../Documentation/Makefile:61: warning: ignoring old recipe for target 'pdfdocs'
>>
>> That's because the code has now two definitions for pdfdocs in
>> case $PDFLATEX command is not found. With the new script, such
>> special case is not needed anymore, as the script checks it.
>>
>> Drop the special case. Even after dropping it, on a machine
>> without LaTeX, it will still produce an error as expected,
>> as running:
>>
>> $ ./tools/docs/sphinx-build-wrapper pdfdocs
>> Error: pdflatex or latexmk required for PDF generation
>>
>> does the check. After applying the patch we have:
>>
>> $ make SPHINXDIRS=peci htmldocs
>> Using alabaster theme
>> Using Python kernel-doc
>>
>> $ make SPHINXDIRS=peci pdfdocs
>> Error: pdflatex or latexmk required for PDF generation
>> make[2]: *** [Documentation/Makefile:64: pdfdocs] Error 1
>> make[1]: *** [/root/Makefile:1808: pdfdocs] Error 2
>> make: *** [Makefile:248: __sub-make] Error 2
>>
>> Which is the expected behavior.
>>
>
> There seems to be a related issue.
>
> At current "docs-mw", under build environments who don't have xelatex nor latexmk,
>
> $ make SPHINXDIRS=peci latexdocs
>
> completes without any issue.
>
> In the resulting .../latex/peci directory, one can run
I meant: .../peci/latex
>
> $ make PDFLATEX="latexmk -xelatex" LATEXOPTS="-interaction=batchmode -no-shell-escape"
>
> and build peci.pdf.
I failed to mention, but of course you need to transfer/share said
.../peci/latex/ to another build environment who has all the required
packages for "pdfdocs".
I often use such heterogeneous combination of running "make latexdocs"
+ running make under each of .../$SPHINXDIRS/latex/ using another
environment.
This way, you need only one set of working texlive packages for testing
against various Sphinx's latex builder releases.
>
> At current "build-scripts", I get this:
>
> $ make SPHINXDIRS=peci latexdocs
> Error: pdflatex or latexmk required for PDF generation
> make[2]: *** [Documentation/Makefile:68: latexdocs] Error 1
> make[1]: *** [<srcdir>/Makefile:1806: latexdocs] Error 2
> make: *** [Makefile:248: __sub-make] Error 2
>
> Patch 2/2 doesn't change the behavior.
>
> This is yet another regression. Please teach sphinx-build-wrapper of the
> fact that "latexdocs" does not run those texlive commands. It is only the
> "pdfdocs" phase that will run them.
>
You see, "make latexdocs" is supposed to generate all the necessary files
for building PDFs to be consumed by make + latexmk/xelatex.
There is a clear boundary between "latexdocs" and "pdfdocs".
Thanks,
Akira
> Regards,
> Akira
>
>> Reported-by: Randy Dunlap <rdunlap@infradead.org>
>> Link: https://lore.kernel.org/linux-doc/e7c29532-71de-496b-a89f-743cef28736e@infradead.org/
>> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
next prev parent reply other threads:[~2025-09-27 9:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 10:16 [PATCH 0/2] some fixes for docs Makefile Mauro Carvalho Chehab
2025-09-26 10:16 ` [PATCH 1/2] tools/docs/sphinx-build-wrapper: allow skipping sphinx-build step Mauro Carvalho Chehab
2025-09-26 10:16 ` [PATCH 2/2] docs: Makefile: avoid a warning when using without texlive Mauro Carvalho Chehab
2025-09-26 19:41 ` Randy Dunlap
2025-09-27 7:35 ` Akira Yokosawa
2025-09-27 9:12 ` Akira Yokosawa [this message]
2025-09-29 8:39 ` Mauro Carvalho Chehab
2025-10-01 12:58 ` [PATCH 0/2] some fixes for docs Makefile Jonathan Corbet
2025-10-01 13:14 ` Mauro Carvalho Chehab
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=1d993906-bae3-41eb-963f-de960cc56dd0@gmail.com \
--to=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®