From: Matthew Wilcox <willy@infradead.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: "Jonathan Corbet" <corbet@lwn.net>,
"Linux Doc Mailing List" <linux-doc@vger.kernel.org>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Alice Ryhl" <aliceryhl@google.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>, "Trevor Gross" <tmgross@umich.edu>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org
Subject: Re: [PATCH v2 3/3] tools/docs: sphinx-* break documentation bulds on openSUSE
Date: Wed, 3 Sep 2025 18:38:37 +0100 [thread overview]
Message-ID: <aLh9HVd8_S9LvSgv@casper.infradead.org> (raw)
In-Reply-To: <29135db8c8094006f256e1fa0b64663c735737e7.1756916565.git.mchehab+huawei@kernel.org>
On Wed, Sep 03, 2025 at 06:24:16PM +0200, Mauro Carvalho Chehab wrote:
> Before this patch, building htmldocs on opensuseLEAP works
> fine:
>
> # make htmldocs
> Available Python versions:
> /usr/bin/python3.11
>
> Python 3.6.15 not supported. Changing to /usr/bin/python3.11
> Python 3.6.15 not supported. Changing to /usr/bin/python3.11
[...]
> 1. after this change, sphinx-pre-install needs to be called
> by hand:
>
> $ /usr/bin/python3.11 tools/docs/sphinx-pre-install
> Detected OS: openSUSE Leap 15.6.
> Sphinx version: 7.2.6
I thought the preferred option was to be able to specify:
PYTHON=/usr/bin/python3.11 make htmldocs
or even make htmldocs PYTHON=/usr/bin/python3.11
like being able to specify CC, LD or AWK.
next prev parent reply other threads:[~2025-09-03 17:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1756916565.git.mchehab+huawei@kernel.org>
2025-09-03 16:24 ` [PATCH v2 3/3] tools/docs: sphinx-* break documentation bulds on openSUSE Mauro Carvalho Chehab
2025-09-03 17:38 ` Matthew Wilcox [this message]
2025-09-04 5:18 ` Mauro Carvalho Chehab
2025-09-03 17:41 ` Randy Dunlap
2025-09-03 19:17 ` 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=aLh9HVd8_S9LvSgv@casper.infradead.org \
--to=willy@infradead.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=corbet@lwn.net \
--cc=gary@garyguo.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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).